> 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
> 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
In response to
pgsql-bugs by date
|Next:||From: Pavel Stehule||Date: 2012-03-05 19:13:03|
|Subject: plpgsql doesn't check a number of expressions and number of target
|Previous:||From: andrre1402||Date: 2012-03-05 16:44:15|
|Subject: BUG #6520: BRT FATAL: COULD NOT CREATE ANY TCP/IP SOCKETS|