[pgpool-hackers: 598] Re: ereport

[Muhammad Usama]

Hi Tatsuo

The idea behind dividing the ereport to multiple lines is to have more
control on amount and verbosity of log generated by pgpool-II (controlled
by log_error_verbosity configuration parameter). I have come across some
pgpool-II logs for debugging the customer end problems which are as large
as 600MB, so I thought this could help in shrinking the output log without
loosing information.

On the second point, I agree that the new log style might confuse some of
the users at first but since PostgreSQL uses the very similar multiline
logs and all pgpool admins are by default familiar with the PG, So they
will adopt it very quickly.

And lastly dividing the report to multiline (DETAIL, HINT ..) gives the
more leverage to throw more descriptive and informative messages to users.

--Usama



On Tue, Aug 19, 2014 at 7:25 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> Usama,
>
> I looked into log generated by new ereport and I noticed now lots of
> log lines are devided into two lines. For example:
>
> 2014-08-19 11:11:23: pid 11326: DEBUG:  authentication backend
> DETAIL:  cp->info[i]:0x7f7c4d8e6000 pid:11575
>
> I'm afraid this makes pgpool admins confused because until 3.3.x, log
> lines are not devided. Is there any reason we should devide log lines
> into two?
>
> Why don't we call ereport without errdetail?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
> _______________________________________________
> pgpool-hackers mailing list
> pgpool-hackers at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20140819/0e5ecec7/attachment.html>