From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: log_destination=file |
Date: | 2017-08-31 12:34:11 |
Message-ID: | 25373.1504182851@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> My understanding is that the main reason for this is that we cannot change
> logging_collector without restarting postmaster, whereas we can change
> log_destination.
Right, because the decision whether to redirect stdout/stderr can't
be changed on the fly.
> My suggestion is we work around this by just always starting the logging
> collector, even if we're not planning to use it.
Umm....
> Do people see an actual problem with that? I agree it's an extra round of
> indirection there, but is that a problem? It would also cause one more
> backgorund process to always be running, but again, is that really a
> problem? The overhead is not exactly large.
You just made three assertions about "this isn't a problem" without
providing any evidence in support of any of them. Maybe with some
measurements we could have a real discussion.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | amul sul | 2017-08-31 12:40:28 | Re: Hash Functions |
Previous Message | Nikolay Shaplov | 2017-08-31 12:29:45 | Re: pgbench tap tests & minor fixes. |