From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: serverlog function (log_destination file) |
Date: | 2004-06-07 13:48:46 |
Message-ID: | 40C4723E.5000204@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>
>
>>Hm, what I missed is that pg_ctl's -l parameter converts to a simple
>>stderr redirection, and it's hardly possible to find out where it's going.
>>This could be solved by a file log_destination option or a
>>freopen(...,stderr) from a guc variable.
>>
>>
>
>Any such patch would be rejected, because it would break the ability
>to pipe stderr into another program (such as logrotate). And what of
>the syslog case?
>
>
>
Might it be sensible to have pg_ctl write its log destination (if any)
out to a file in the data dir? That plus the log_destination setting
might provide enough info at least for some common cases.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2004-06-07 13:57:08 | Re: [pgsql-hackers-win32] Failures with windows port |
Previous Message | Dave Page | 2004-06-07 13:44:53 | Re: serverlog function (log_destination file) |