From: Tom Lane <tgl@sss.pgh.pa.us>
To: depesz@depesz.com
cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Logs vanish after partial log destination change
In-reply-to: <20210905112832.GA8707@depesz.com>
References: <20210905112832.GA8707@depesz.com>
Comments: In-reply-to hubert depesz lubaczewski <depesz@depesz.com>
	message dated "Sun, 05 Sep 2021 13:28:33 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2872656.1630851875.1@sss.pgh.pa.us>
Date: Sun, 05 Sep 2021 10:24:35 -0400
Message-ID: <2872657.1630851875@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2872657.1630851875%40sss.pgh.pa.us>
Precedence: bulk

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