Skip site navigation (1) Skip section navigation (2)

Re: BUG #6518: archive_command stderr not in log if log_destination=syslog

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: vygen(at)kicktipp(dot)de
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6518: archive_command stderr not in log if log_destination=syslog
Date: 2012-03-05 18:22:48
Message-ID: 23628.1330971768@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
vygen(at)kicktipp(dot)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

In response to

pgsql-bugs by date

Next:From: Pavel StehuleDate: 2012-03-05 19:13:03
Subject: plpgsql doesn't check a number of expressions and number of target variables correctly
Previous:From: andrre1402Date: 2012-03-05 16:44:15
Subject: BUG #6520: BRT FATAL: COULD NOT CREATE ANY TCP/IP SOCKETS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group