RE: libpq debug log

From: "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>
To: 'Peter Eisentraut' <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "'Yugo Nagata'" <nagata(at)sraoss(dot)co(dot)jp>
Subject: RE: libpq debug log
Date: 2018-09-26 01:24:37
Message-ID: 71E660EB361DF14299875B198D4CE5423DE5ADB3@g01jpexmbkw25
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


Sorry for my late response.

> Between perf/systemtap/dtrace and wireshark, you can already do pretty much
> all of that. Have you looked at those and found anything missing?

These commands provide detailed information to us.
However, I think the trace log is necessary from the following point.

1. ease of use for users
It is necessary to take information that is easy to understand for database users.
This trace log is retrieved on the application server side.
Not only the database developer but also application developer will get and check this log.
Also, some of these commands return detailed PostgreSQL function names.
The trace log would be useful for users who do not know the inside of PostgreSQL (e.g. application developers)

2. obtain the same information on all OS
Some commands depend on the OS.
I think that it is important that the trace log information is compatible to each OS.

Aya Iwata

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-09-26 01:29:08 Re: Shared buffer access rule violations?
Previous Message Kyotaro HORIGUCHI 2018-09-26 00:55:09 Re: shared-memory based stats collector