From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Iwata, Aya <iwata.aya@jp.fujitsu.com>
To: Yugo Nagata <nagata@sraoss.co.jp>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: libpq debug log
Date: Fri, 7 Sep 2018 15:28:10 +0200
Message-ID: <4bc9abbd-44a0-1787-b410-4e68b5ab3228@2ndquadrant.com> (raw)
In-Reply-To: <71E660EB361DF14299875B198D4CE5423DE4A154@g01jpexmbkw25>
References: <71E660EB361DF14299875B198D4CE5423DE3FBA4@g01jpexmbkw25>
<20180827215124.0cdb4d0cb99136b5a86b1d9f@sraoss.co.jp>
<71E660EB361DF14299875B198D4CE5423DE4A154@g01jpexmbkw25>
On 04/09/2018 02:29, Iwata, Aya wrote:
> Since I'd like to monitor the information the server and the client exchange,
> I think monitoring protocol messages is good.
>
> When a slow query is occurs, we check this client side trace log.
> The purpose of this log acquisition I thought is to identify where is the problem:
> server side, application side or traffic.
> And if the problem is in application side, checking the trace log to identify what is the problem.
Between perf/systemtap/dtrace and wireshark, you can already do pretty
much all of that. Have you looked at those and found anything missing?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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: peter.eisentraut@2ndquadrant.com, iwata.aya@jp.fujitsu.com, nagata@sraoss.co.jp
Subject: Re: libpq debug log
In-Reply-To: <4bc9abbd-44a0-1787-b410-4e68b5ab3228@2ndquadrant.com>
* 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