Re: Unpredictable shark slowdown after migrating to 8.4 - Mailing list pgsql-hackers

From Sergey Konoplev
Subject Re: Unpredictable shark slowdown after migrating to 8.4
Date
Msg-id c3a7de1f0911170822x3904b666v371ae663e95cd738@mail.gmail.com
Whole thread Raw
In response to Re: Unpredictable shark slowdown after migrating to 8.4  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Unpredictable shark slowdown after migrating to 8.4
List pgsql-hackers
On Mon, Nov 16, 2009 at 9:56 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> Sergey Konoplev escribió:
>
>> I tried to get locks with this queries
>
> Did you try pg_locks?
>

I tried monitor locks with pgrowlocks. Isn't it better way? If it
isn't what points should I pay attention with pg_lock?

I've just write the query

SELECT pid, count(1) AS locks, current_query
FROM pg_locks AS l LEFT JOIN pg_stat_activity AS a ON pid = procpid
WHERE l.mode IN ('RowExclusiveLock', 'ShareUpdateExclusiveLock',
'ExclusiveLock')
GROUP BY 1,3 ORDER BY 2 DESC LIMIT 10;

would it be what we need?

--
Regards,
Sergey Konoplev


pgsql-hackers by date:

Previous
From: Emmanuel Cecchet
Date:
Subject: Re: Partitioning option for COPY
Next
From: Sergey Konoplev
Date:
Subject: Re: Unpredictable shark slowdown after migrating to 8.4