Oliver Elphick <olly@xxxxxxxxxx> writes: > On 9 August 2013 02:49, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> I wonder whether we shouldn't change the syslogger to emit something to >> stderr when it takes over logging, saying "logging is now redirected to >> <someplace>". > Shouldn't you also, or instead, log to stderr just before leaving it, in > case the configuration of the new logging is faulty? I think the faulty-config case is (mostly?) covered already, in that we check validity of GUC values before installing them. The point of this proposal is just to remind people that the "original" log file might not be all the log output there is. The cases that I've seen seemed to usually involve package installations where people weren't really aware of the nondefault logging choices that the packager had made. Anyway, there's a concrete patch proposal in pgsql-hackers, at http://www.postgresql.org/message-id/11372.1376015537@xxxxxxxxxxxxx Please comment on that if you want to discuss details. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
