libpq debug log - Mailing list pgsql-hackers

From Iwata, Aya
Subject libpq debug log
Date
Msg-id 71E660EB361DF14299875B198D4CE5423DE3FBA4@g01jpexmbkw25
Whole thread Raw
Responses Re: libpq debug log
Re: libpq debug log
List pgsql-hackers
Hi,

I'm going to propose libpq debug log for analysis of queries on the application side.
I think that it is useful to determine whether the cause is on the application side or the server side when a slow
queryoccurs. 
 

The provided information is "date and time" at which execution of processing is started, "query", "application side
processing",which is picked up information from PQtrace(), and "connection id", which is for uniquely identifying the
connection.
 

To collect the log, set the connection string or environment variable.
- logdir or PGLOGDIR : directory where log file written
- logsize or PGLOGSIZE : maximum log size

What do you think about this?  Do you think that such feature is necessary?

Regards, 
Aya Iwata



pgsql-hackers by date:

Previous
From: Tatsuro Yamada
Date:
Subject: Re: Fix help option of contrib/oid2name
Next
From: Tatsuro Yamada
Date:
Subject: Re: [HACKERS] CLUSTER command progress monitor