| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_basebackup on slave running for a long time |
| Date: | 2016-11-21 07:10:28 |
| Message-ID: | 26db6b96-35aa-b245-b560-9c5d381143ef@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/20/2016 11:00 PM, Subhankar Chattopadhyay wrote:
>
> Yes so if the slave is behind I need to start over pgbasebackup. I saw
> according to the documentation this query gives us the replication
> state. Can somebody tell me if this would be sufficient to know if I
> need to start over the backup ?
>
>
if the slave is behind but is catching up, no, restarting replication
would be overkill. only if the slave gets so far behind that it can't
catch up, and in that case, a wal archive would be a better choice than
a new base backup.
I've never run into these problems as I run on dedicated hardware
servers, which don't have all these reliability and performance
problems. a complete server failure requiring a full rebuild is
something that would happen less than annually.
--
john r pierce, recycling bits in santa cruz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Terrius | 2016-11-21 10:32:21 | Re: Partial update on an postgres upsert violates constraint |
| Previous Message | Subhankar Chattopadhyay | 2016-11-21 07:00:45 | Re: pg_basebackup on slave running for a long time |