Re: Logs vanish after partial log destination change - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Logs vanish after partial log destination change
Date
Msg-id 2872657.1630851875@sss.pgh.pa.us
Whole thread Raw
In response to Logs vanish after partial log destination change  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: Logs vanish after partial log destination change  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-bugs
hubert depesz lubaczewski <depesz@depesz.com> writes:
> I start with:
> log_destination = 'syslog'
> logging_collector = false

> Logs to to syslog, all is well.

> Then, I chance log_destination to 'csvlog' and logging_collector to
> 'on'.

> And then I reload config.

> I know I can chance log_destination, but I can't change
> logging_collector. I assumed it means that logging will go to where they
> did before.

No.  You effectively set log_destination to empty, since the csvlog
item is ignored if the logging collector isn't active.  That's not
a case that we should disallow, IMO.  I do not think there's anything
that we can do here that wouldn't make other use-cases worse.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17182: Race condition on concurrent DROP and CREATE of dependent object
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: Logs vanish after partial log destination change