On Fri, Aug 14, 2015 at 3:50 PM, Andres Freund <[email protected]> wrote:
> On 2015-08-14 15:32:17 +0900, Michael Paquier wrote:
>> 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.
>
> Feel free to send a patch.

I don't mind giving it a try if time allows... CREATE_REPLICATION_SLOT
IDENT K_PHYSICAL slot_options? With slot_options: (reserve = on/off)?
And, actually, here is an unrelated patch, the docs are referring to
confirmed_flush instead of confirmed_flush_lsn ;)
-- 
Michael
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 1e895e4..b4ea227 100644
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -5579,7 +5579,7 @@
      </row>
 
      <row>
-      <entry><structfield>confirmed_flush</structfield></entry>
+      <entry><structfield>confirmed_flush_lsn</structfield></entry>
       <entry><type>pg_lsn</type></entry>
       <entry></entry>
       <entry>The address (<literal>LSN</literal>) up to which the logical
-- 
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Reply via email to