I think I figured this out after some playing around.
Looks like postgres only redirects stderr to its log files. Consistent with what documentation says, and my findings playing around.
In my situation, I was looking for sysout of my python archiver to go to postgres log files.Looks like postgres only redirects stderr to its log files. Consistent with what documentation says, and my findings playing around.
On Wed, May 28, 2014 at 1:30 PM, Marc Brazeau <litespeedmarc@xxxxxxxxx> wrote:
- And I lose context (from having sysouts along side other Postgres message).- I don't get any of the log_rotation- Not sure it will work with Services (thoughI haven't tried).Only way to get output from my archive_command, is with the -l option on pg_ctl start. But this has issues:So I'm sure I'm doing something wrong, or this is maybe a novice question,And awesome, my postgres log files get the output from my archive command.
On My Mac, I set log_collector=on, archive_command='echo hello %p %f'
On Windows, this does not work (Using postgres 9.3..4)
Surely there is a simple answer here?