Re: Unpredictable shark slowdown after migrating to 8.4

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unpredictable shark slowdown after migrating to 8.4
Date: 2009-11-17 16:22:29
Message-ID: c3a7de1f0911170822x3904b666v371ae663e95cd738@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 16, 2009 at 9:56 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sergey Konoplev 2009-11-17 16:34:44 Re: Unpredictable shark slowdown after migrating to 8.4
Previous Message Emmanuel Cecchet 2009-11-17 16:19:35 Re: Partitioning option for COPY