Re: [HACKERS] log_destination=file
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] log_destination=file |
Дата | |
Msg-id | 25373.1504182851@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | [HACKERS] log_destination=file (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: [HACKERS] log_destination=file
|
Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.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
В списке pgsql-hackers по дате отправления: