From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Including replication slot data in base backups |
Date: | 2014-04-02 00:29:18 |
Message-ID: | 533B59DE.3060603@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/01/2014 05:24 AM, Michael Paquier wrote:
> Hi all,
>
> As of now, pg_basebackup creates an empty repository for pg_replslot/
> in a base backup, forcing the user to recreate slots on other nodes of
> the cluster with pg_create_*_replication_slot, or copy pg_replslot
> from another node. This is not really user-friendly especially after a
> failover where a given slave may not have the replication slot
> information of the master that it is replacing.
>
> The simple patch attached adds a new option in pg_basebackup, called
> --replication-slot, allowing to include replication slot information
> in a base backup. This is done by extending the command BASE_BACKUP in
> the replication protocol.
>
> As it is too late for 9.4, I would like to add it to the first commit
> fest of 9.5. Comments are welcome.
Assuming it works, this seems like something we need to fix for 9.4. No?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-04-02 00:53:47 | It seems no Windows buildfarm members are running find_typedefs |
Previous Message | Merlin Moncure | 2014-04-01 23:28:43 | Re: using arrays within structure in ECPG |