| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logs vanish after partial log destination change |
| Date: | 2021-09-05 14:24:35 |
| Message-ID: | 2872657.1630851875@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> 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.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2021-09-06 07:57:10 | Re: Logs vanish after partial log destination change |
| Previous Message | Tom Lane | 2021-09-05 14:15:37 | Re: BUG #17182: Race condition on concurrent DROP and CREATE of dependent object |