Re: Logs vanish after partial log destination change

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Logs vanish after partial log destination change
Date: 2021-09-06 07:57:10
Message-ID: 20210906075710.GA22522@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pawel Kudzia 2021-09-06 08:18:45 Re: BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows
Previous Message Tom Lane 2021-09-05 14:24:35 Re: Logs vanish after partial log destination change