From: | "btober(at)computer(dot)org" <btober(at)broadstripe(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Why does this hot standy archive_command work |
Date: | 2017-01-21 03:03:07 |
Message-ID: | 479858649.146809718.1484967787671.JavaMail.zimbra@broadstripe.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
While learning a bit about basic hot standby configuration, I was reviewing an article that used these parameters
wal_level = 'hot_standby'
archive_mode = on
archive_command = 'cd .'
max_wal_senders = 1
hot_standby = on
How or why that particular archive_command actually works (... and it does ... I tried it ...) is not clear to me based on reading of the Postgresql documentation on this topic. I would have expected to see an actual copy or rsync command, as described in the fine manual at section 25.3.1. "Setting Up WAL Archiving"
The entire example appears at
Can anyone enlighten on this topic, or provide a link to an existing explanation?
-- B
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2017-01-21 03:11:12 | Re: Why does this hot standy archive_command work |
Previous Message | Kevin Grittner | 2017-01-20 18:18:44 | Re: update error with serializable |