## Nick Renders (postg...@arcict.com):
> I was wondering if anyone had any good tips for "debugging" the
> archive_command in the postgresql.conf.
For starters, you get rather noisy logging when that command fails
(plus all the output from the command itself), so check your postgres
logfile first
Hello,
I was wondering if anyone had any good tips for "debugging" the archive_command
in the postgresql.conf.
I want to see what certain settings are when the command is run, like $PATH and
id, but I don't want it to be successful either, so that the WAL files remain
untouched.
Any tips?
Th
