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

From hubert depesz lubaczewski
Subject Re: Logs vanish after partial log destination change
Date
Msg-id 20210906075710.GA22522@depesz.com
Whole thread Raw
In response to Re: Logs vanish after partial log destination change  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Logs vanish after partial log destination change
Next
From: Pawel Kudzia
Date:
Subject: Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows