Re: Postgresql Logging - Mailing list pgsql-general

From Bruce Momjian
Subject Re: Postgresql Logging
Date
Msg-id 200405261846.i4QIk1Z01523@candle.pha.pa.us
Whole thread Raw
In response to Postgresql Logging  (Ericson Smith <eric@did-it.com>)
Responses Re: Postgresql Logging  (Ericson Smith <eric@did-it.com>)
List pgsql-general
Ericson Smith wrote:
> Hi,
>
> Currently we are logging SQL statements for profiling purposes. We now
> get something like this:
>
> 2004-05-26 13:27:51 [30017] LOG:  statement: SELECT * FROM cache_62
> WHERE key='6832271710644150012240e7153b6f62'
> 2004-05-26 13:27:51 [30017] LOG:  duration: 0.733 ms
>
> Is there a way to get the duration into the statement line as well?
> Sometimes the logging overlaps, so its difficult to decide which
> duration applies to which statement, even though the have the PID in there.

Sure, set log_min_duration_statement to 0.  That is new in 7.4.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-general by date:

Previous
From: Ericson Smith
Date:
Subject: Postgresql Logging
Next
From: Dennis Bjorklund
Date:
Subject: Re: performance very slow