From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | "ascot(dot)moss(at)gmail(dot)com" <ascot(dot)moss(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Enable WAL Archive in Replication server |
Date: | 2013-08-11 22:45:59 |
Message-ID: | CAB7nPqT66_xBAk1XzQ2-LUALMX_thErgKCYs8oN9HfmEtadZ5Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Aug 12, 2013 at 1:53 AM, ascot(dot)moss(at)gmail(dot)com
<ascot(dot)moss(at)gmail(dot)com> wrote:
> I want to enable WAL archive on the replica, I am advised that WAL archive
> can only be enabled on the Master, can you please advise if this is a bug
> and any workaround available?
Archiving a WAL file is only done once its generation has been
completed by a master server. A standby node only replays WAL files,
copying them from the indicated archive folder with restore_command to
its local pg_xlog folder when necessary, and performs no archive
actions.
http://www.postgresql.org/docs/devel/static/continuous-archiving.html#BACKUP-ARCHIVING-WAL
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Romain Billon-Grand | 2013-08-12 06:01:44 | Re: BUG #8335: trim() un-document behaviour |
Previous Message | ascot.moss@gmail.com | 2013-08-11 16:53:24 | Enable WAL Archive in Replication server |