Search Postgresql Archives

Re: lock contention, need profiling idea

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 1, 2014 at 2:28 PM, Jeff Janes <jeff.janes@xxxxxxxxx> 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



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux