> on db server. They are quite powerful 2 processor xeon w/ 6Gig of ram .
> Couple of days ago we had a serious performance hit and the db server (pg.
> v7.4) was overloaded w/ something in a way that operating system was almost
> not able to respond or in cases it did not.
> After some analysis i suspect that there is a query that takes up to 1
> second and that is the cause. Upon each page loading this query fires and
> takes the one second and blocks the page to load completly . The load was
> roughly ~300 connections in one minute .
> So here are my questions :
> · Why does the second and the later queries take the whole on second
> if the dataset is the same . Shouldn't PG realise that the query is the same
> so i give the user the same resultset ?
> · How do I know if one query blocks the other ?
> · Is there a way to log the long running queries in 7.4 ? If not is
> it available in any newer version ?
Can you post the queries? Can you provide an 'analyze explain'? Do you
perform a 'vacuum analyze' on a regular basis?
When lenity and cruelty play for a kingdom,
the gentlest gamester is the soonest winner.
Sent via pgsql-performance mailing list (firstname.lastname@example.org)
To make changes to your subscription: