RE: libpq debug log - Mailing list pgsql-hackers

From Iwata, Aya
Subject RE: libpq debug log
Date
Msg-id 71E660EB361DF14299875B198D4CE5423DE5ADB3@g01jpexmbkw25
Whole thread Raw
In response to Re: libpq debug log  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses RE: libpq debug log  ("Iwata, Aya" <iwata.aya@jp.fujitsu.com>)
List pgsql-hackers
Hi, 

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.

Regards,
Aya Iwata



pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: shared-memory based stats collector
Next
From: Thomas Munro
Date:
Subject: Re: Shared buffer access rule violations?