[email protected] 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

-- 
Sent via pgsql-bugs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Reply via email to