|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||"Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>|
|Subject:||Re: libpq debug log|
|Views:||Raw Message | Whole Thread | Download mbox|
"Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com> writes:
> 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.
Hm, how will you tell that really? And what's the advantage over the
existing server-side query logging capability?
> 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.
PQtrace() is utterly useless for anything except debugging libpq
internals, and it's not tremendously useful even for that. Don't
bother with that part.
Where will you get a "unique connection id" from?
How will you deal with asynchronously-executed queries --- either
the PQgetResult style, or the single-row-at-a-time style?
regards, tom lane
|Next Message||Michael Paquier||2018-08-24 13:55:52||Re: document that MergeAppend can now prune|
|Previous Message||Etsuro Fujita||2018-08-24 12:45:35||Re: Problem while updating a foreign table pointing to a partitioned table on foreign server|