Re: Enable logging requires restart

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enable logging requires restart
Date: 2010-09-24 12:17:41
Message-ID: AANLkTim9OZDHDsqg=LWum4H1N2P3k6xxth33YXEd9C9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 24, 2010 at 4:33 AM, Thom Brown <thom(at)linux(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2010-09-24 12:22:12 Re: Enable logging requires restart
Previous Message Robert Haas 2010-09-24 12:13:54 Re: patch: SQL/MED(FDW) DDL