Skip site navigation (1) Skip section navigation (2)

Re: Postgresql Logging

From: Ericson Smith <eric(at)did-it(dot)com>
To:
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgresql Logging
Date: 2004-05-26 19:59:42
Message-ID: 40B4F72E.3090705@did-it.com (view raw or flat)
Thread:
Lists: pgsql-general
Exactly what I need. Thanks a lot.

- Ericson

Bruce Momjian wrote:

>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.
>
>  
>

Attachment: eric.vcf
Description: text/x-vcard (315 bytes)

In response to

pgsql-general by date

Next:From: Sean ShannyDate: 2004-05-26 20:00:37
Subject: Problem with sequences on a reload of a pg_dump file
Previous:From: mack paulDate: 2004-05-26 19:23:24
Subject: temas del comando COPY

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group