| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Jinhua Luo <luajit(dot)io(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Does logical replication slot itself would be physically replicated to slaves? |
| Date: | 2018-09-08 20:07:21 |
| Message-ID: | 20180908200721.GA19122@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 08, 2018 at 05:37:43PM +0800, Jinhua Luo wrote:
> The logical streaming replication is used to replicate changes between
> DC. I need to confirm that whether the logical replication slot would
> be saved in wal and replicated to slave via physical replication? So
> that in case of failover, the new master still holds the slot needed
> by peer.
Replication slot creation is not an operation WAL-logged. Please note
that slots are not kept in base backups when taking them using the
replication protocol (see basebackup.c for the list of things filtered),
so as the standby or the new instance deployed with this base backup
does not bloat pg_wal with data which may not be around anymore.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-09-08 20:21:34 | Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace |
| Previous Message | Michael Paquier | 2018-09-08 19:53:03 | Re: Prevent concurrent DROP SCHEMA when certain objects are being initially created in the namespace |