Re: log_destination

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Christoph Berg <cb(at)df7cb(dot)de>, "pgsql-pkg-debian(at)postgresql(dot)org" <pgsql-pkg-debian(at)postgresql(dot)org>
Subject: Re: log_destination
Date: 2013-03-06 11:02:01
Message-ID: CABUevEy_1wzOimT99L19jq1T5TNyU8=YmHw2SSwnYLAyfHoivA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-pkg-debian

On Wed, Mar 6, 2013 at 11:37 AM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
> Re: Andres Freund 2013-03-06 <20130306102405(dot)GL13803(at)alap2(dot)anarazel(dot)de>
>> Both pg_ctl and the logging collector seem to open files in O_APPEND
>> mode. So - provided we could figure out the correct filename - they
>> could just log to the same file.
>
> Probably impossible with %y-%m-%d style log files, because of the
> variable filename as such, and you will still get a stale/later unused
> fd pointing at the -l file after log switch.
>
> One solution could be not to use -l at all, which has the advantage
> that you get "I can't start" type errors at the console instead of the
> misleading "Server starting" message while in fact there are fatal
> errors waiting for you in the log. (On the other hand, you will
> probably still want a log file for those in non-interactive startups.)

The RPMs use a separate "startup.log" (I think that's what it's called
- or at least something similar). While not ideal, I think that's a
fairly reasonable workaround for that issue. Startup issues aren't
that common - and it's not unreasonable to look in "startup.log" if
things don't start, I think...

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-pkg-debian by date

  From Date Subject
Next Message Peter Eisentraut 2013-03-07 14:59:45 Re: log_destination
Previous Message Christoph Berg 2013-03-06 10:37:55 Re: log_destination