From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Enable logging requires restart |
Date: | 2010-09-24 12:31:06 |
Message-ID: | AANLkTimh3d7zhJ7R-_ygTgSh-RjQq9zfcQWH6rSnr54P@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 24 September 2010 13:22, Thom Brown <thom(at)linux(dot)com> wrote:
> On 24 September 2010 13:17, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 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.
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-09-24 12:38:15 | Re: Configuring synchronous replication |
Previous Message | Thom Brown | 2010-09-24 12:22:12 | Re: Enable logging requires restart |