Logs vanish after partial log destination change

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Logs vanish after partial log destination change
Date: 2021-09-05 11:28:33
Message-ID: 20210905112832.GA8707@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,
I'm not entirely sure if it's a bug, or what, but it caught me by
surprise.

Tested it on Linux, on 12.6 and 15devel.

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.

But - logs are gone.
They are not in syslog. They are not in the new location.

When I tried it on test system with 15devel, I noticed by chance that
logs were redirected to terminal from which I issued `pg_ctl reload`
from. Well, that's hardly useful.

I'm not entirely sure what Pg should do in such case, perhaps just
restrict changing any log_* if one of changed gucs require restart?

But, it caught me by surprise, and figured that it might be problematic
for others too.

Best regards,

depesz

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-09-05 14:15:37 Re: BUG #17182: Race condition on concurrent DROP and CREATE of dependent object
Previous Message PG Bug reporting form 2021-09-04 06:00:00 BUG #17182: Race condition on concurrent DROP and CREATE of dependent object