RE: libpq debug log

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

I created a new version patch. Please find attached my patch.

Changes:
Since v2 patch
I forgot to write the detail of v2 patch changes. So I write these.
- Fixed the " Start receiving message from backend:" message location. Because I found that message located at outside
of"retry4". 
 
- Changed location where output "start :" / "end :" messages and timestamp. The reason of the change is that v1 patch
didnot correspond to Asynchronous Command Processing.
 
- Added documentation
- Added documentation how to check mistake of logdir and/or logsize. (Based on review comment of Jim san's)
Since v3 patch
- Fixed my mistake on fe-connect.c. Time and message were output at the place where does not output in originally
PQtrace().These messages are needed only new trace log. So I fixed it.
 
- Fixed two points so that new trace log overlaps all places in PQtrace(). (Based on review comment of Jacob san's)

TODO:
I will add the feature called "logging level" on next version patch. I will attach it as soon as possible.

I'm marking it as "Needs review".

Regards,
Aya Iwata

Вложения

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

Предыдущее
От: rajan
Дата:
Сообщение: vacuum and autovacuum - is it good to configure the threshold atTABLE LEVEL?
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: dsa_allocate() faliure