Re: Enable logging requires restart

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: Enable logging requires restart
Дата
Msg-id AANLkTimh3d7zhJ7R-_ygTgSh-RjQq9zfcQWH6rSnr54P@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Enable logging requires restart  (Thom Brown <thom@linux.com>)
Ответы Re: Enable logging requires restart  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 24 September 2010 13:22, Thom Brown <thom@linux.com> wrote:
> On 24 September 2010 13:17, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Fri, Sep 24, 2010 at 4:33 AM, Thom Brown <thom@linux.com> wrote:
>>> At the moment, to enable logging, a service restart is required.  Is
>>> there any way to remove this requirement or is there a fundamental
>>> reason why it must always be like that?
>>
>> Are you speaking of the logging_collector GUC?  I think the difficulty
>> is - if you wanted to turn this on without a restart, how would you
>> get the collector's stdin to be each backend's stdout/stderr?  I don't
>> see any way to do it, actually.
>
> This is probably blasphemy, but "off" would log to a symbolic link
> pointing to /dev/null, which is repointed to a log_file if reloaded
> with "on"?

No, this is horrible.  I take it back.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Thom Brown
Дата:
Сообщение: Re: Enable logging requires restart
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Configuring synchronous replication