Re: improve release-note for pg_current_logfile()

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: nagata(at)sraoss(dot)co(dot)jp
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: improve release-note for pg_current_logfile()
Date: 2017-06-19 00:13:57
Message-ID: 20170619.091357.982049524406670859.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> Add function pg_current_logfile() to read syslog's current stderr and csvlog output file names (Gilles Darold)
>>
>> This confused me because "syslog" is one of method for logging as well
>> as stderr and csvlog. I guess it is intended syslogger, but I think that
>> "logging collector" is more convenient for users because this is used in
>> the pg_current_logfile() documentation.
>
> His proposal is changing the line above to:
>
> Add function pg_current_logfile() to read logging collector's current stderr and csvlog output file names (Gilles Darold)
>
> Looks reasonable fix to me. If there's no objection, I will commit
> this.

Done.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2017-06-19 02:30:22 Re: Something is rotten in publication drop
Previous Message Tomas Vondra 2017-06-18 23:08:22 Re: Parallel Aggregation support for aggregate functions that use transitions not implemented for array_agg