| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | "psql performance list" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: measure database contention |
| Date: | 2008-12-17 14:18:54 |
| Message-ID: | 603c8f070812170618g3116a90du94cbf102f0336d59@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Dec 16, 2008 at 2:32 PM, Jaime Casanova
<jcasanov(at)systemguards(dot)com(dot)ec> wrote:
> we have a some bad queries (developers are working on that), some of
> them run in 17 secs and that is the average but when analyzing logs i
> found that from time to time some of them took upto 3 mins (the same
> query that normally runs in 17secs).
>
> so my question is: how could i look for contention problems?
Is it the exact same query? Sometimes you might find that the query
plan changes depending on the particular values you have in there; it
is worth running "EXPLAIN ANALYZE" to look for such cases.
You might also want to look at pg_locks.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2008-12-17 14:49:26 | Re: measure database contention |
| Previous Message | Albe Laurenz | 2008-12-17 07:34:23 | Re: measure database contention |