pg_ctl and stderr

From: "Ed L(dot)" <pgsql(at)bluepolka(dot)net>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: pg_ctl and stderr
Date: 2004-11-11 07:13:14
Message-ID: 200411110013.14013.pgsql@bluepolka.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On 7.4.6 and earlier, we use apache's log rotation program as follows:

pg_ctl start | rotatelogs ...

If we have a configuration failure, say a bad parameter in postgresql.conf,
we often don't quickly notice because it goes to stdout (into the log).

It'd be nice if it went to stderr as well so we could see it without having
to search the log, but that wouldn't work if we wanted to capture stderr in
the logs (do normal ERROR messages go to stderr?).

Just curious how folks make pg_ctl start-up failures obvious while also
piping to apache rotatelogs?

Ed

Browse pgsql-general by date

  From Date Subject
Next Message Björn Platzen 2004-11-11 07:13:16 Can't insert date in field with foreign key
Previous Message Rolf stvik 2004-11-11 06:35:10 Re: Important Info on comp.databases.postgresql.general