On Tue, Jul 1, 2014 at 2:28 PM, Jeff Janes <jeff.ja...@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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
