Re: pgsql: Allow pg_create_physical_replication_slot() to reserve WAL. - Mailing list pgsql-committers

From Michael Paquier
Subject Re: pgsql: Allow pg_create_physical_replication_slot() to reserve WAL.
Date
Msg-id CAB7nPqSwONSfu2Pk_p7kticomS4_4juG8UwAmATqzita7bVsxQ@mail.gmail.com
Whole thread Raw
In response to pgsql: Allow pg_create_physical_replication_slot() to reserve WAL.  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: Allow pg_create_physical_replication_slot() to reserve WAL.  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
On Tue, Aug 11, 2015 at 7:47 PM, Andres Freund <andres@anarazel.de> wrote:
> Allow pg_create_physical_replication_slot() to reserve WAL.
>
> When creating a physical slot it's often useful to immediately reserve
> the current WAL position instead of only doing after the first feedback
> message arrives. That e.g. allows slots to guarantee that all the WAL
> for a base backup will be available afterwards.
>
> Logical slots already have to reserve WAL during creation, so generalize
> that logic into being usable for both physical and logical slots.

Why hasn't this addition been spread as well in the replication
protocol? It seems to me that most of the refactoring work has been
done with ReplicationSlotReserveWal.
--
Michael


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: PL/Python: Make tests pass with Python 3.5
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Allow pg_create_physical_replication_slot() to reserve WAL.