paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-17 12:21:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

puppet: Use the correct Postgres archive command

Browse Source 
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)
This commit is contained in:
Zev Benjamin
2013-05-08 17:05:30 -04:00
parent bf82fadc95
commit 1b6514b89f
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
servers/puppet/modules/humbug/files/postgresql/postgresql.conf.master
View File

@@ -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 </dev/null'
archive_command = '/usr/local/bin/env-wal-e wal-push %p'
# Standby replication settings (ignored on master)
hot_standby = on

2
servers/puppet/modules/humbug/files/postgresql/postgresql.conf.slave
View File

@@ -586,7 +586,7 @@ log_autovacuum_min_duration = 100
wal_level = hot_standby
max_wal_senders = 2
archive_mode = on
archive_command = 'cp -f %p /var/lib/postgresql/9.1/main/archive/%f </dev/null'
archive_command = '/usr/local/bin/env-wal-e wal-push %p'
# Standby replication settings (ignored on master)
hot_standby = on