BUG #6518: archive_command stderr not in log if log_destination=syslog
The following bug has been logged on the website:
Bug reference: 6518
Logged by: Janning Vygen
Email address: vygen@kicktipp.de
PostgreSQL version: 9.1.2
Operating system: Linux / Debian
Description:
I am using postgresql 9.1.2 from debian backports.
The documentation for 9.1 says about archive_command:
"Any messages written to stderr from the script will appear in the database
server log, allowing complex configurations to be diagnosed easily if they
fail."
<http://www.postgresql.org/docs/9.1/static/continuous-archiving.html#BACKUP-TIPS>
This is not true if log_destination=syslog
Messages to sdterr does not appear at all anywhere. I prefer syslog because
of pgfouine.
Great if it can be fixed. At least this should be documented.
kind regards
Janning
vygen@kicktipp.de writes:
The documentation for 9.1 says about archive_command:
"Any messages written to stderr from the script will appear in the database
server log, allowing complex configurations to be diagnosed easily if they
fail."
<http://www.postgresql.org/docs/9.1/static/continuous-archiving.html#BACKUP-TIPS>
This is not true if log_destination=syslog
Yes, that's poorly worded --- you have to be using output to stderr for
this to work as the docs claim.
Messages to sdterr does not appear at all anywhere. I prefer syslog because
of pgfouine.
Great if it can be fixed. At least this should be documented.
There really isn't any way that we can force stderr output from a script
to magically go to syslog. But we can at least clarify the docs, and
I will go do so. Thanks for the report!
regards, tom lane
Excerpts from vygen's message of lun mar 05 09:14:26 -0300 2012:
Messages to sdterr does not appear at all anywhere. I prefer syslog because
of pgfouine.
FWIW I think pgfouine is perfectly capable of using stderr logs now.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support