Re: lock contention, need profiling idea - Mailing list pgsql-general

From Merlin Moncure
Subject Re: lock contention, need profiling idea
Date
Msg-id CAHyXU0wFXrxBkAMmv6a3pt1jr7t8Fh5waMSvHor1cZC-xock5w@mail.gmail.com
Whole thread Raw
In response to Re: lock contention, need profiling idea  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
On Tue, Jul 1, 2014 at 2:28 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
>> You should have a look at pg_stat_activity, pg_prepared_xacts and pg_locks
>> to get more information about the transactions running and the locks being
>> taken.
>
> In 9.4, the log message will also include info on the blocking
> process, not just the blocked process, for lock waits.
>
> But until then, pg_stat_activity and pg_locks are the best bet.
> Unless you can afford to turn log_statement to 'all' and dig through
> the resulting mess.

log_min_duration_statement might be a middle ground -- set it to 1
second plus.  on most applications this should cut out most of the
chaff.

merlin


pgsql-general by date:

Previous
From: Kynn Jones
Date:
Subject: Re: how to create a role with no privileges?
Next
From: Paul Jungwirth
Date:
Subject: hstore to json and back again