| From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
|---|---|
| To: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, thomas simon <tsimon(at)neteven(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Pg_basebackup does not do aything |
| Date: | 2014-06-26 17:16:04 |
| Message-ID: | 53AC5554.2030603@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
From your last message:
> It is recommended to configure it to grab archive files from somewhere (can be from other node) if you have archiving enabled. So, if the receiver can't keep up with the sender
> (e.g. when the WAL files are rotated and the sender does not have the files the receiver wants anymore), it can get the files it need from archiving.
>
According to the postgresql documentation at 25.2.3 Preparing the Master for Standby Servers, Set up continuous archiving on the primary to an archive directory accessible from the
standby.
I took this to mean the archive_command = "scp %p postgres@<IP of standby>:/<directory on standby>"
And yes, you can add a ";" at the end of this and specify a second server. That's what I'm doing. Oh, and you have to setup ssh keyrings so the scp will not prompt for a password.
Anyway, I got the impression that the primary should push and the standby's should not pull WAL segments from this part of the docs. Although, I can see how you could just specify
the scp in the restore_command and do the pull. I just don't know the safety of doing that.
--
Jay
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver | 2014-06-27 12:55:13 | Re: [pgadmin-support] Best backup strategy for production systems |
| Previous Message | John Scalia | 2014-06-26 16:48:44 | Re: Wal archive way behind in streaming replication |