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

Поиск
Список
Период
Сортировка
От vygen@kicktipp.de
Тема BUG #6518: archive_command stderr not in log if log_destination=syslog
Дата
Msg-id E1S4Wo6-0001f5-Oq@wrigleys.postgresql.org
обсуждение исходный текст
Ответы Re: BUG #6518: archive_command stderr not in log if log_destination=syslog  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #6518: archive_command stderr not in log if log_destination=syslog  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-bugs
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:=20=20=20=20=20=20=20=20

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=3Dsyslog

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=20
Janning

В списке pgsql-bugs по дате отправления:

Предыдущее
От: marko@kobaz.net
Дата:
Сообщение: BUG #6511: calling spi_exec_query from non-main package, results in: couldn't fetch $_TD
Следующее
От: sanker.ks@gmail.com
Дата:
Сообщение: BUG #6515: mount data folder in remote location