Hi Gilles,
On Tue, 15 Nov 2016 15:15:52 -0600
"Karl O. Pinc" <k...@meme.com> wrote:
> > On Mon, 7 Nov 2016 23:29:28 +0100
> > Gilles Darold <gilles.dar...@dalibo.com> wrote:
> > > - Do not write current_logfiles when log_collector is activated
> > > but log_destination doesn't contained stderr or csvlog. This was
> > > creating an empty file that can confuse the user.
> Whether to write current_logfiles only when there's a stderr or csvlog
> seems dependent up on whether the current_logfiles file is for human
> or program use. If for humans, don't write it unless it has content.
> If for programs, why make the program always have to check to see
> if the file exists before reading it? Failing to check is just one
> more cause of bugs.
What are your thoughts on this? I'm leaning toward current_logfiles
being for programs, not people. So it should be present whenever
logging_collector is on.
Regards,
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
