| From: | vygen(at)kicktipp(dot)de |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #6518: archive_command stderr not in log if log_destination=syslog |
| Date: | 2012-03-05 12:14:26 |
| Message-ID: | E1S4Wo6-0001f5-Oq@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 6518
Logged by: Janning Vygen
Email address: vygen(at)kicktipp(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | llima15 | 2012-03-05 12:25:33 | BUG #6519: Server doesn't listem |
| Previous Message | rene.vanpaassen | 2012-03-05 11:52:24 | BUG #6517: Volatile function erroneously optimized, does not consider change in schema path |