RE: libpq debug log

Поиск
Список
Период
Сортировка
От Iwata, Aya
Тема RE: libpq debug log
Дата
Msg-id 71E660EB361DF14299875B198D4CE5423DEB9E4B@g01jpexmbkw25
обсуждение исходный текст
Ответ на RE: libpq debug log  ("Iwata, Aya" <iwata.aya@jp.fujitsu.com>)
Ответы RE: libpq debug log  ("Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>)
Список pgsql-hackers
Hi,

I have developed a new libpq trace logging aimed at checking which side (server or client) is causing the performance
issue.

The new libpq trace log can do the following things;
- Setting whether to get log or not by using connection strings or environment variables. It means that application
sourcecode changes is not needed to get the log.
 
- Getting time when receive and send process start/end. Functions too.
- Setting log level; When level1(default) is set, it outputs the time in the function and connection time. When level2
isset, it outputs information on the protocol message being exchanged, in addition to level1 information.
 

I updated patch, but I am not sure if these changes and implementation are correct or not. So I need your comment and
advice.
I would appreciate your advice and develop/fix my patch further.

Regards,
Aya Iwata

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Log a sample of transactions
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: PSA: we lack TAP test coverage on NetBSD and OpenBSD