Hi, Basically I do not want to touch my Master while performing PITR. So here what I am trying to achieve now in my development environment. 1.
Take base backup from slave 2.
Do WAL archiving from master 3.
Try to up postgresql using base backup from slave and wal archives from master. I don’t know, if this will work or not. But my final goal is to setup entire PITR process using base backup from slave. Thanks & Regards, Vicky Soni From: Scott Whitney [mailto:scott@xxxxxxxxxxx]
Hi, Dave. It depends on what you're trying to do. If you want a slave up in real-time replication mode, that's by far the simplest setup. The concept is: 1) start a backup select pg_start_backup("myslave"),true); 2) Rsync (or tar) your pg data directory over to your slave. 3) select pg_stop_backup(); 4) Tell your slave how to connect to the master Start your slave. This is a pretty straight-forward link for this: https://opensourcedbms.com/dbms/how-to-do-point-in-time-recovery-with-postgresql-9-2-pitr-3/
If you want to do something "clever," like offset how far behind the slave is, that's more complex. From:
pgsql-admin-owner@xxxxxxxxxxxxxx <pgsql-admin-owner@xxxxxxxxxxxxxx> on behalf of Dave Johansen <davejohansen@xxxxxxxxx> On Tue, May 24, 2016 at 6:05 AM, Vicky Soni - Quipment India <vicky.soni@xxxxxxxxxxx> wrote:
The standby/slave is read only and does not generate WAL files (it only consumes them to stay in sync with the master). Journyx, Inc. 7600 Burnet Road #300 p 512.834.8888 f 512-834-8858 Do you receive our promotional emails? You can subscribe or unsubscribe to those emails at
http://go.journyx.com/emailPreference/e/4932/714/ |