From: hubert depesz lubaczewski <depesz@depesz.com>
To: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Logs vanish after partial log destination change
Date: Sun, 5 Sep 2021 13:28:33 +0200
Message-ID: <20210905112832.GA8707@depesz.com> (raw)
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
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, pgsql-bugs@lists.postgresql.org
Subject: Re: Logs vanish after partial log destination change
In-Reply-To: <20210905112832.GA8707@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