| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-docs(at)postgresql(dot)org> |
| Subject: | archive_command vs recovery_command paths |
| Date: | 2014-02-13 00:20:02 |
| Message-ID: | 52FC0FB2.1030705@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Hi folks
Another point of confusion I've been seeing a lot in users on Stack
Overflow, dba.stackexchange.com, etc surrounds the meaning of paths
given in archive_command and restore_command.
Lots of people seem to assume that they are both relative to the master,
and that the master will run the restore_command to fetch archives to
send to the replica on request.
(Yes, I know that's completely missing the point of archive-based
replication, but it seems common).
So I think docs changes are needed to the explanations of those options,
and to the replication/recovery section, that better explain that we
assume there's shared storage like NFS involved, and if there isn't you
need to use commands like scp/rsync instead, or use tools like WAL-E.
I'm not going to get time to do this one for at least a few days, but
I'm posting it now partly so I don't forget about it.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-13 00:25:29 | Re: Links for upgraders |
| Previous Message | Craig Ringer | 2014-02-13 00:15:59 | Re: PATCH: Warn users about tablespace abuse data loss risk |