pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bryce Nesbitt <bryce2@obviously.com>
To: pgsql-sql@postgresql.org
Subject: "slow lock" log in addition to log_min_duration_statement ?
Date: Wed, 10 Nov 2010 12:28:46 -0800
Message-ID: <4CDB007E.7010904@obviously.com> (raw)

I have a cluster with log_min_duration_statement set to log slow 
queries. Presently what I'm tracking down is almost certainly a lock 
problem.  Is there any analog of log_min_duration_statement for locks?  
If there is a lock on a certain critical tables for more than a few 
hundredths of a second I want to know.

Similarly in pg_stat_activity, is there a way to get the parameters to 
the current_query?  I see the placeholders (e.g. $1, $2) but not the data.

This is with PostgreSQL 8.3.4
Thanks!



view thread (2+ messages)  latest in thread

Message-ID: <4CDB007E.7010904@obviously.com>
Permalink:  ../4CDB007E.7010904@obviously.com/
Also on:    postgresql.org/message-id/4CDB007E.7010904@obviously.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: bryce2@obviously.com
  Subject: Re: "slow lock" log in addition to log_min_duration_statement ?
  In-Reply-To: <4CDB007E.7010904@obviously.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox