Date: Mon, 6 Sep 2021 09:57:10 +0200
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Logs vanish after partial log destination change
Message-ID: <20210906075710.GA22522@depesz.com>
Reply-To: depesz@depesz.com
References: <20210905112832.GA8707@depesz.com>
 <2872657.1630851875@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <2872657.1630851875@sss.pgh.pa.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210906075710.GA22522%40depesz.com>
Precedence: bulk

On Sun, Sep 05, 2021 at 10:24:35AM -0400, Tom Lane wrote:
> > 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.

Well, OK. Thanks,

depesz