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

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

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: patch: SQL/MED(FDW) DDL
Next
From: Thom Brown
Date:
Subject: Re: Enable logging requires restart