From 1b6514b89f41e6314b11f91709c9877c48fd875c Mon Sep 17 00:00:00 2001 From: Zev Benjamin Date: Wed, 8 May 2013 17:05:30 -0400 Subject: [PATCH] puppet: Use the correct Postgres archive command I hadn't changed it previously out of paranoia in the case we had a faulty failover and had two masters both uploading to the same place. However, I now don't think this can happen, as recovery completion will cause Postgres to start a new timeline. (imported from commit d58f1aa306eff4f6fd950664ff658539c1249bdf) --- .../modules/humbug/files/postgresql/postgresql.conf.master | 2 +- .../modules/humbug/files/postgresql/postgresql.conf.slave | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/servers/puppet/modules/humbug/files/postgresql/postgresql.conf.master b/servers/puppet/modules/humbug/files/postgresql/postgresql.conf.master index 6b1106bde3..1a925d8071 100644 --- a/servers/puppet/modules/humbug/files/postgresql/postgresql.conf.master +++ b/servers/puppet/modules/humbug/files/postgresql/postgresql.conf.master @@ -590,7 +590,7 @@ log_autovacuum_min_duration = 100 wal_level = hot_standby max_wal_senders = 5 archive_mode = on -archive_command = 'cp -f %p /var/lib/postgresql/9.1/main/archive/%f