Re: Replication slot on master failure - Mailing list pgsql-general

From Michael Paquier
Subject Re: Replication slot on master failure
Date
Msg-id CAB7nPqT0FDEL5RMZHPOX7QVYJG2DQ0xea+t84RGf+BOPCJ3bug@mail.gmail.com
Whole thread Raw
In response to Replication slot on master failure  (hariprasath nallasamy <hariprasathnallasamy@gmail.com>)
List pgsql-general
On Mon, Sep 26, 2016 at 7:49 PM, hariprasath nallasamy
<hariprasathnallasamy@gmail.com> wrote:
>        We are using replication slot for capturing some change sets to
> update dependent tables.
>        Will there be inconsistency if the master fails and the standby takes
> the role of master.?

Replication slot creation is not replicated to standbys if that's what
you are looking for. So if you use a slot on master and consume its
data up to a given point, and then promote a standby, you may see a
gap of data after creating a slot, or if you created a slot previously
you may consume twice the same WAL records. Note that replication
slots created on standbys are initialized from the last checkpoint
redo record, so you could take advantage of this property before
promoting a standby.
--
Michael


pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Large pg_xlog
Next
From: Patrick B
Date:
Subject: Update two tables returning id from insert CTE Query