From: hubert depesz lubaczewski <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
Date: Mon, 6 Sep 2021 09:57:10 +0200
Message-ID: <20210906075710.GA22522@depesz.com> (raw)
In-Reply-To: <2872657.1630851875@sss.pgh.pa.us>
References: <20210905112832.GA8707@depesz.com>
<2872657.1630851875@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: depesz@depesz.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: Logs vanish after partial log destination change
In-Reply-To: <20210906075710.GA22522@depesz.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox