Tom Lane wrote:
Andreas Pflug <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
