From: | James Sewell <james(dot)sewell(at)lisasoft(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | WAL archive on slave |
Date: | 2014-02-07 05:35:26 |
Message-ID: | CANkGpBuD4xDW+gFLA7a-=i03-XT2uwtJQbsmFa=nGWMeTWhvgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
My understanding is that WAL archiving can not be enabled on the slave in a
streaming replication pair.
If this is correct, is there a reason behind it? I can see logs showing up
in pg_xlog, so could they not be archived?
The reason I ask is if this happened it would allow the following with a
streaming replication pair (A,B):
1. Start A as master
2. Attach B as slave using basebackup
3. work ....
4. Promote B to master
5. Restore A from a scheduled backup to a time before promotion
6. Attach A as slave pointing at B's WAL archive
If we used A's WAL archive in this case and A had writes after the
promotion then we would get timeline errors.
As far as I can tell, using the WAL archive from B would resolve this issue.
Or have I missed something here?
Cheers,
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________
Level 2, 50 Queen St, Melbourne VIC 3000
*P *(+61) 3 8370 8000 *W* www.lisasoft.com *F *(+61) 3 8370 8099
--
------------------------------
The contents of this email are confidential and may be subject to legal or
professional privilege and copyright. No representation is made that this
email is free of viruses or other defects. If you have received this
communication in error, you may not copy or distribute any part of it or
otherwise disclose its contents to anyone. Please advise the sender of your
incorrect receipt of this correspondence.
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2014-02-07 05:45:21 | Re: password-less access, without using pg_hba |
Previous Message | Reece Hart | 2014-02-07 05:12:13 | Re: password-less access, without using pg_hba |