[pgpool-general: 8044] Re: Logging verbosity level of newly forwarded ParameterStatus messages

Syed Ahmed syed at merchlogix.com
Thu Mar 10 22:46:20 JST 2022


That would be really helpful, anything under 'WARNING' would solve my
problem.

Thanks,
Syed A.

On Thu, Mar 10, 2022 at 3:24 AM Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > Referenced commit:
> >
> https://github.com/pgpool/pgpool2/commit/4bcba5258130c3cd9f855157a4359aad2fa7acfc?diff=split
> >
> > It looks like it bumped from "DEBUG5" to "LOG" level which means I have
> to
> > set my log_min_messages to FATAL to avoid "application_name",
> > "session_authorization", "is_superuser" spam because of the way our
> > connections are done.
> >
> > Example messages (imagine thousands of these):
> > 2022-03-09 13:48:26 yy at yy tutorials#search 39889 [27994] LOG:
> >  ParameterStatus message from backend: 0
> > 2022-03-09 13:48:26 yy at yy tutorials#search 39889 [27994] DETAIL:
> parameter
> > name: "application_name" value: ""
> >
> > Would it be possible to reduce the level for this log so I can go back to
> > the default of "WARNING" for the log_min_messages parameter?
>
> No. Maybe I should change the log level back to DEBUG5?
>
> Best reagards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20220310/9249a9a2/attachment.htm>


More information about the pgpool-general mailing list