pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedCREATE_REPLICATION_SLOT exported snapshot
2+ messages / 2 participants
[nested] [flat]
* CREATE_REPLICATION_SLOT exported snapshot
@ 2016-09-11 10:23 Marko Tiikkaja <marko@joh.to>
2017-02-02 21:07 ` Re: CREATE_REPLICATION_SLOT exported snapshot Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 1 reply; 2+ messages in thread
From: Marko Tiikkaja @ 2016-09-11 10:23 UTC (permalink / raw)
To: pgsql-docs
Hi,
There's a brief mention of CREATE_REPLICATION_SLOT exporting a snapshot
here:
https://www.postgresql.org/docs/devel/static/logicaldecoding-explanation.html#AEN71570
but how to access the snapshot identifier is not documented anywhere.
So I came up with the attached patch (against master). Please have a
looksie.
.m
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Attachments:
create_replication_slot_result.v1.patch (text/x-patch, 1.8K) download
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
index 68b0941..6bf8354 100644
--- a/doc/src/sgml/protocol.sgml
+++ b/doc/src/sgml/protocol.sgml
@@ -1475,6 +1475,49 @@ The commands accepted in walsender mode are:
</listitem>
</varlistentry>
</variablelist>
+ <para>
+ In response to this command, the server will send a one-row result set
+ containing the following fields:
+ <variablelist>
+ <varlistentry>
+ <term><literal>slot_name</literal> (<type>text</type>)</term>
+ <listitem>
+ <para>
+ The name of the newly-created replication slot.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>consistent_point</literal> (<type>text</type>)</term>
+ <listitem>
+ <para>
+ The WAL position at which the slot became consistent. This is the
+ earliest location from which streaming can start on this replication
+ slot.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>snapshot_name</literal> (<type>text</type>)</term>
+ <listitem>
+ <para>
+ The identifier of the snapshot exported by the command. The snapshot
+ is valid until a new command is executed or the replication connection is
+ closed. NULL if the created slot is physical.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><literal>output_plugin</literal> (<type>text</type>)</term>
+ <listitem>
+ <para>
+ The name of the output plugin used by the newly-created replication
+ slot. NULL if the created slot is physical.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
</listitem>
</varlistentry>
* Re: CREATE_REPLICATION_SLOT exported snapshot
2016-09-11 10:23 CREATE_REPLICATION_SLOT exported snapshot Marko Tiikkaja <marko@joh.to>
@ 2017-02-02 21:07 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
0 siblings, 0 replies; 2+ messages in thread
From: Peter Eisentraut @ 2017-02-02 21:07 UTC (permalink / raw)
To: Marko Tiikkaja <marko@joh.to>; pgsql-docs
On 9/11/16 6:23 AM, Marko Tiikkaja wrote:
> There's a brief mention of CREATE_REPLICATION_SLOT exporting a snapshot
> here:
>
> https://www.postgresql.org/docs/devel/static/logicaldecoding-explanation.html#AEN71570
>
> but how to access the snapshot identifier is not documented anywhere.
> So I came up with the attached patch (against master). Please have a
> looksie.
committed
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2017-02-02 21:07 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-09-11 10:23 CREATE_REPLICATION_SLOT exported snapshot Marko Tiikkaja <marko@joh.to>
2017-02-02 21:07 ` Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox