RE: libpq debug log

From: "Iwata, Aya" <iwata(dot)aya(at)jp(dot)fujitsu(dot)com>
To: 'Haribabu Kommi' <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, "nagata(at)sraoss(dot)co(dot)jp" <nagata(at)sraoss(dot)co(dot)jp>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: RE: libpq debug log
Date: 2018-11-21 09:03:02
Message-ID: 71E660EB361DF14299875B198D4CE5423DE80454@g01jpexmbkw25
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Hari san,

Thank you for your comment! And sorry my late reply…

>I have some comments related to the trace output that is getting
>printed. The amount of log it is generating may not be understood
>to many of the application developers. IMO, this should print
>only the necessary information that can understood by any one
>by default and full log with more configuration?

I understand. And I agree your opinion.
I will add feature called “log level” that changes the amount of log output information with my future version patch.

Regards,
Aya Iwata

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Iwata, Aya 2018-11-21 09:53:46 RE: libpq debug log
Previous Message REIX, Tony 2018-11-21 08:45:12 RE: Shared Memory: How to use SYSV rather than MMAP ?