From: Tom Lane <tgl@sss.pgh.pa.us>
To: Iwata, Aya <iwata.aya@jp.fujitsu.com>
Cc: 'Yugo Nagata' <nagata@sraoss.co.jp>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: libpq debug log
Date: Mon, 03 Sep 2018 20:57:33 -0400
Message-ID: <25440.1536022653@sss.pgh.pa.us> (raw)
In-Reply-To: <71E660EB361DF14299875B198D4CE5423DE4A154@g01jpexmbkw25>
References: <71E660EB361DF14299875B198D4CE5423DE3FBA4@g01jpexmbkw25>
<20180827215124.0cdb4d0cb99136b5a86b1d9f@sraoss.co.jp>
<71E660EB361DF14299875B198D4CE5423DE4A154@g01jpexmbkw25>
"Iwata, Aya" <iwata.aya@jp.fujitsu.com> writes:
> The purpose of this log acquisition I thought is to identify where is the problem:
> server side, application side or traffic.
TBH, I think the sort of logging you're proposing would be expensive
enough that *it* would be the bottleneck in a lot of cases. A lot
of people find that the existing server-side "log_statement" support
is too expensive to keep turned on in production --- and that logs only
received SQL queries, not the returned data, and certainly not every
message passed over the wire.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, iwata.aya@jp.fujitsu.com, nagata@sraoss.co.jp
Subject: Re: libpq debug log
In-Reply-To: <25440.1536022653@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox