From: | "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | libpq debug log |
Date: | 2018-08-24 04:38:22 |
Message-ID: | 71E660EB361DF14299875B198D4CE5423DE3FBA4@g01jpexmbkw25 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 query occurs.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuro Yamada | 2018-08-24 05:04:15 | Re: [HACKERS] CLUSTER command progress monitor |
Previous Message | Tatsuro Yamada | 2018-08-24 04:32:47 | Re: Fix help option of contrib/oid2name |