>>> "Joshua D. Drake" <[EMAIL PROTECTED]> wrote: > It certainly makes more sense to do this: > > archive_mode = on > pg_ctl reload > > archive_mode = off > pg_ctl reload > > versus > > archive_command = '/path/to/really/long/archive/string' > pg_ctl reload > > archive_command = '/bin/true' > pg_ctl reload Hmmm... If there's no significant performance difference between archive_mode = on archive_command = '/bin/true' and archive_mode = off archive_command = '/archive/command/used/during/snapshot/backups' I could live with diddling the command to control archiving. It doesn't log anything extra when archive_mode is on? Why is it safer to change archive_command to a no-op on the fly than to turn off archive mode? -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
