Re: Enable logging requires restart - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Enable logging requires restart
Date
Msg-id AANLkTinZdNG=TkPyQF4S9rEwcYfp97irA9pqeEto7E=m@mail.gmail.com
Whole thread Raw
In response to Re: Enable logging requires restart  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Enable logging requires restart
Re: Enable logging requires restart
List pgsql-hackers
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"?

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Enable logging requires restart
Next
From: Thom Brown
Date:
Subject: Re: Enable logging requires restart