2017-01-19 18:00:00 +01:00
|
|
|
<!--
|
|
|
|
doc/src/sgml/ref/create_subscription.sgml
|
|
|
|
PostgreSQL documentation
|
|
|
|
-->
|
|
|
|
|
2017-10-20 03:16:39 +02:00
|
|
|
<refentry id="sql-createsubscription">
|
2017-01-19 18:00:00 +01:00
|
|
|
<indexterm zone="sql-createsubscription">
|
|
|
|
<primary>CREATE SUBSCRIPTION</primary>
|
|
|
|
</indexterm>
|
|
|
|
|
|
|
|
<refmeta>
|
|
|
|
<refentrytitle>CREATE SUBSCRIPTION</refentrytitle>
|
|
|
|
<manvolnum>7</manvolnum>
|
|
|
|
<refmiscinfo>SQL - Language Statements</refmiscinfo>
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
|
|
|
<refname>CREATE SUBSCRIPTION</refname>
|
|
|
|
<refpurpose>define a new subscription</refpurpose>
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<synopsis>
|
2017-10-09 04:00:57 +02:00
|
|
|
CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceable>
|
|
|
|
CONNECTION '<replaceable class="parameter">conninfo</replaceable>'
|
|
|
|
PUBLICATION <replaceable class="parameter">publication_name</replaceable> [, ...]
|
2017-05-12 14:57:01 +02:00
|
|
|
[ WITH ( <replaceable class="parameter">subscription_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] ) ]
|
2017-01-19 18:00:00 +01:00
|
|
|
</synopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</title>
|
|
|
|
|
|
|
|
<para>
|
2017-06-17 16:21:41 +02:00
|
|
|
<command>CREATE SUBSCRIPTION</command> adds a new subscription for the
|
2017-01-19 18:00:00 +01:00
|
|
|
current database. The subscription name must be distinct from the name of
|
|
|
|
any existing subscription in the database.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The subscription represents a replication connection to the publisher. As
|
|
|
|
such this command does not only add definitions in the local catalogs but
|
|
|
|
also creates a replication slot on the publisher.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
A logical replication worker will be started to replicate data for the new
|
|
|
|
subscription at the commit of the transaction where this command is run.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2018-11-03 17:21:54 +01:00
|
|
|
Additional information about subscriptions and logical replication as a
|
|
|
|
whole is available at <xref linkend="logical-replication-subscription"/> and
|
2017-11-23 15:39:47 +01:00
|
|
|
<xref linkend="logical-replication"/>.
|
2017-01-19 18:00:00 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Parameters</title>
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="parameter">subscription_name</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The name of the new subscription.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>CONNECTION '<replaceable class="parameter">conninfo</replaceable>'</literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-02-08 03:26:50 +01:00
|
|
|
The connection string to the publisher. For details
|
2017-11-23 15:39:47 +01:00
|
|
|
see <xref linkend="libpq-connstring"/>.
|
2017-01-19 18:00:00 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>PUBLICATION <replaceable class="parameter">publication_name</replaceable></literal></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2017-05-12 14:57:01 +02:00
|
|
|
Names of the publications on the publisher to subscribe to.
|
2017-03-23 13:36:36 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2017-04-14 19:58:46 +02:00
|
|
|
<varlistentry>
|
2017-05-12 14:57:01 +02:00
|
|
|
<term><literal>WITH ( <replaceable class="parameter">subscription_parameter</replaceable> [= <replaceable class="parameter">value</replaceable>] [, ... ] )</literal></term>
|
2017-04-14 19:58:46 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2021-09-13 04:59:10 +02:00
|
|
|
This clause specifies optional parameters for a subscription.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The following parameters control what happens during subscription creation:
|
2017-05-12 14:57:01 +02:00
|
|
|
|
|
|
|
<variablelist>
|
2021-09-13 04:59:10 +02:00
|
|
|
|
2017-05-12 14:57:01 +02:00
|
|
|
<varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
<term><literal>connect</literal> (<type>boolean</type>)</term>
|
2017-05-12 14:57:01 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2021-09-13 04:59:10 +02:00
|
|
|
Specifies whether the <command>CREATE SUBSCRIPTION</command>
|
|
|
|
should connect to the publisher at all. Setting this to
|
|
|
|
<literal>false</literal> will change default values of
|
|
|
|
<literal>enabled</literal>, <literal>create_slot</literal> and
|
|
|
|
<literal>copy_data</literal> to <literal>false</literal>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
It is not allowed to combine <literal>connect</literal> set to
|
|
|
|
<literal>false</literal> and <literal>enabled</literal>,
|
|
|
|
<literal>create_slot</literal>, or <literal>copy_data</literal>
|
|
|
|
set to <literal>true</literal>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Since no connection is made when this option is set
|
|
|
|
to <literal>false</literal>, the tables are not subscribed, and so
|
|
|
|
after you enable the subscription nothing will be replicated.
|
|
|
|
It is required to run
|
|
|
|
<literal>ALTER SUBSCRIPTION ... REFRESH PUBLICATION</literal> in order
|
|
|
|
for tables to be subscribed.
|
2017-05-12 14:57:01 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>create_slot</literal> (<type>boolean</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies whether the command should create the replication slot on
|
|
|
|
the publisher. The default is <literal>true</literal>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>enabled</literal> (<type>boolean</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies whether the subscription should be actively replicating,
|
|
|
|
or whether it should be just setup but not started yet. The default
|
|
|
|
is <literal>true</literal>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>slot_name</literal> (<type>string</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Name of the replication slot to use. The default behavior is to
|
|
|
|
use the name of the subscription for the slot name.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When <literal>slot_name</literal> is set to
|
|
|
|
<literal>NONE</literal>, there will be no replication slot
|
|
|
|
associated with the subscription. This can be used if the
|
|
|
|
replication slot will be created later manually. Such
|
|
|
|
subscriptions must also have both <literal>enabled</literal> and
|
|
|
|
<literal>create_slot</literal> set to <literal>false</literal>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
2017-05-12 14:57:01 +02:00
|
|
|
|
2021-09-13 04:59:10 +02:00
|
|
|
<para>
|
|
|
|
The following parameters control the replication behavior:
|
2017-05-12 14:57:01 +02:00
|
|
|
|
2021-09-13 04:59:10 +02:00
|
|
|
<variablelist>
|
2017-05-12 14:57:01 +02:00
|
|
|
|
2020-07-18 18:44:51 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><literal>binary</literal> (<type>boolean</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies whether the subscription will request the publisher to
|
|
|
|
send the data in binary format (as opposed to text).
|
|
|
|
The default is <literal>false</literal>.
|
|
|
|
Even when this option is enabled, only data types that have
|
|
|
|
binary send and receive functions will be transferred in binary.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When doing cross-version replication, it could happen that the
|
|
|
|
publisher has a binary send function for some data type, but the
|
|
|
|
subscriber lacks a binary receive function for the type. In
|
|
|
|
such a case, data transfer will fail, and
|
|
|
|
the <literal>binary</literal> option cannot be used.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2017-05-12 14:57:01 +02:00
|
|
|
<varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
<term><literal>copy_data</literal> (<type>boolean</type>)</term>
|
2017-05-12 14:57:01 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2021-09-13 04:59:10 +02:00
|
|
|
Specifies whether the existing data in the publications that are
|
|
|
|
being subscribed to should be copied once the replication starts.
|
|
|
|
The default is <literal>true</literal>.
|
2017-05-12 14:57:01 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
|
Add support for streaming to built-in logical replication.
To add support for streaming of in-progress transactions into the
built-in logical replication, we need to do three things:
* Extend the logical replication protocol, so identify in-progress
transactions, and allow adding additional bits of information (e.g.
XID of subtransactions).
* Modify the output plugin (pgoutput) to implement the new stream
API callbacks, by leveraging the extended replication protocol.
* Modify the replication apply worker, to properly handle streamed
in-progress transaction by spilling the data to disk and then
replaying them on commit.
We however must explicitly disable streaming replication during
replication slot creation, even if the plugin supports it. We
don't need to replicate the changes accumulated during this phase,
and moreover we don't have a replication connection open so we
don't have where to send the data anyway.
Author: Tomas Vondra, Dilip Kumar and Amit Kapila
Reviewed-by: Amit Kapila, Kuntal Ghosh and Ajin Cherian
Tested-by: Neha Sharma, Mahendra Singh Thalor and Ajin Cherian
Discussion: https://postgr.es/m/688b0b7f-2f6c-d827-c27b-216a8e3ea700@2ndquadrant.com
2020-09-03 04:24:07 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><literal>streaming</literal> (<type>boolean</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies whether streaming of in-progress transactions should
|
|
|
|
be enabled for this subscription. By default, all transactions
|
|
|
|
are fully decoded on the publisher, and only then sent to the
|
|
|
|
subscriber as a whole.
|
|
|
|
</para>
|
2021-09-13 04:59:10 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term><literal>synchronous_commit</literal> (<type>enum</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
The value of this parameter overrides the
|
|
|
|
<xref linkend="guc-synchronous-commit"/> setting within this
|
|
|
|
subscription's apply worker processes. The default value
|
|
|
|
is <literal>off</literal>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
It is safe to use <literal>off</literal> for logical replication:
|
|
|
|
If the subscriber loses transactions because of missing
|
|
|
|
synchronization, the data will be sent again from the publisher.
|
|
|
|
</para>
|
Add support for prepared transactions to built-in logical replication.
To add support for streaming transactions at prepare time into the
built-in logical replication, we need to do the following things:
* Modify the output plugin (pgoutput) to implement the new two-phase API
callbacks, by leveraging the extended replication protocol.
* Modify the replication apply worker, to properly handle two-phase
transactions by replaying them on prepare.
* Add a new SUBSCRIPTION option "two_phase" to allow users to enable
two-phase transactions. We enable the two_phase once the initial data sync
is over.
We however must explicitly disable replication of two-phase transactions
during replication slot creation, even if the plugin supports it. We
don't need to replicate the changes accumulated during this phase,
and moreover, we don't have a replication connection open so we don't know
where to send the data anyway.
The streaming option is not allowed with this new two_phase option. This
can be done as a separate patch.
We don't allow to toggle two_phase option of a subscription because it can
lead to an inconsistent replica. For the same reason, we don't allow to
refresh the publication once the two_phase is enabled for a subscription
unless copy_data option is false.
Author: Peter Smith, Ajin Cherian and Amit Kapila based on previous work by Nikhil Sontakke and Stas Kelvich
Reviewed-by: Amit Kapila, Sawada Masahiko, Vignesh C, Dilip Kumar, Takamichi Osumi, Greg Nancarrow
Tested-By: Haiying Tang
Discussion: https://postgr.es/m/02DA5F5E-CECE-4D9C-8B4B-418077E2C010@postgrespro.ru
Discussion: https://postgr.es/m/CAA4eK1+opiV4aFTmWWUF9h_32=HfPOW9vZASHarT0UA5oBrtGw@mail.gmail.com
2021-07-14 04:03:50 +02:00
|
|
|
|
2021-09-13 04:59:10 +02:00
|
|
|
<para>
|
|
|
|
A different setting might be appropriate when doing synchronous
|
|
|
|
logical replication. The logical replication workers report the
|
|
|
|
positions of writes and flushes to the publisher, and when using
|
|
|
|
synchronous replication, the publisher will wait for the actual
|
|
|
|
flush. This means that setting
|
|
|
|
<literal>synchronous_commit</literal> for the subscriber to
|
|
|
|
<literal>off</literal> when the subscription is used for
|
|
|
|
synchronous replication might increase the latency for
|
|
|
|
<command>COMMIT</command> on the publisher. In this scenario, it
|
|
|
|
can be advantageous to set <literal>synchronous_commit</literal>
|
|
|
|
to <literal>local</literal> or higher.
|
|
|
|
</para>
|
Add support for prepared transactions to built-in logical replication.
To add support for streaming transactions at prepare time into the
built-in logical replication, we need to do the following things:
* Modify the output plugin (pgoutput) to implement the new two-phase API
callbacks, by leveraging the extended replication protocol.
* Modify the replication apply worker, to properly handle two-phase
transactions by replaying them on prepare.
* Add a new SUBSCRIPTION option "two_phase" to allow users to enable
two-phase transactions. We enable the two_phase once the initial data sync
is over.
We however must explicitly disable replication of two-phase transactions
during replication slot creation, even if the plugin supports it. We
don't need to replicate the changes accumulated during this phase,
and moreover, we don't have a replication connection open so we don't know
where to send the data anyway.
The streaming option is not allowed with this new two_phase option. This
can be done as a separate patch.
We don't allow to toggle two_phase option of a subscription because it can
lead to an inconsistent replica. For the same reason, we don't allow to
refresh the publication once the two_phase is enabled for a subscription
unless copy_data option is false.
Author: Peter Smith, Ajin Cherian and Amit Kapila based on previous work by Nikhil Sontakke and Stas Kelvich
Reviewed-by: Amit Kapila, Sawada Masahiko, Vignesh C, Dilip Kumar, Takamichi Osumi, Greg Nancarrow
Tested-By: Haiying Tang
Discussion: https://postgr.es/m/02DA5F5E-CECE-4D9C-8B4B-418077E2C010@postgrespro.ru
Discussion: https://postgr.es/m/CAA4eK1+opiV4aFTmWWUF9h_32=HfPOW9vZASHarT0UA5oBrtGw@mail.gmail.com
2021-07-14 04:03:50 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
|
Add support for prepared transactions to built-in logical replication.
To add support for streaming transactions at prepare time into the
built-in logical replication, we need to do the following things:
* Modify the output plugin (pgoutput) to implement the new two-phase API
callbacks, by leveraging the extended replication protocol.
* Modify the replication apply worker, to properly handle two-phase
transactions by replaying them on prepare.
* Add a new SUBSCRIPTION option "two_phase" to allow users to enable
two-phase transactions. We enable the two_phase once the initial data sync
is over.
We however must explicitly disable replication of two-phase transactions
during replication slot creation, even if the plugin supports it. We
don't need to replicate the changes accumulated during this phase,
and moreover, we don't have a replication connection open so we don't know
where to send the data anyway.
The streaming option is not allowed with this new two_phase option. This
can be done as a separate patch.
We don't allow to toggle two_phase option of a subscription because it can
lead to an inconsistent replica. For the same reason, we don't allow to
refresh the publication once the two_phase is enabled for a subscription
unless copy_data option is false.
Author: Peter Smith, Ajin Cherian and Amit Kapila based on previous work by Nikhil Sontakke and Stas Kelvich
Reviewed-by: Amit Kapila, Sawada Masahiko, Vignesh C, Dilip Kumar, Takamichi Osumi, Greg Nancarrow
Tested-By: Haiying Tang
Discussion: https://postgr.es/m/02DA5F5E-CECE-4D9C-8B4B-418077E2C010@postgrespro.ru
Discussion: https://postgr.es/m/CAA4eK1+opiV4aFTmWWUF9h_32=HfPOW9vZASHarT0UA5oBrtGw@mail.gmail.com
2021-07-14 04:03:50 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term><literal>two_phase</literal> (<type>boolean</type>)</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies whether two-phase commit is enabled for this subscription.
|
|
|
|
The default is <literal>false</literal>.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When two-phase commit is enabled then the decoded transactions are sent
|
|
|
|
to the subscriber on the PREPARE TRANSACTION. By default, the transaction
|
|
|
|
prepared on the publisher is decoded as a normal transaction at commit.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
The two-phase commit implementation requires that the replication has
|
|
|
|
successfully passed the initial table synchronization phase. This means
|
|
|
|
even when two_phase is enabled for the subscription, the internal
|
|
|
|
two-phase state remains temporarily "pending" until the initialization
|
|
|
|
phase is completed. See column
|
|
|
|
<literal>subtwophasestate</literal> of <xref linkend="catalog-pg-subscription"/>
|
|
|
|
to know the actual two-phase state.
|
|
|
|
</para>
|
|
|
|
|
Add support for streaming to built-in logical replication.
To add support for streaming of in-progress transactions into the
built-in logical replication, we need to do three things:
* Extend the logical replication protocol, so identify in-progress
transactions, and allow adding additional bits of information (e.g.
XID of subtransactions).
* Modify the output plugin (pgoutput) to implement the new stream
API callbacks, by leveraging the extended replication protocol.
* Modify the replication apply worker, to properly handle streamed
in-progress transaction by spilling the data to disk and then
replaying them on commit.
We however must explicitly disable streaming replication during
replication slot creation, even if the plugin supports it. We
don't need to replicate the changes accumulated during this phase,
and moreover we don't have a replication connection open so we
don't have where to send the data anyway.
Author: Tomas Vondra, Dilip Kumar and Amit Kapila
Reviewed-by: Amit Kapila, Kuntal Ghosh and Ajin Cherian
Tested-by: Neha Sharma, Mahendra Singh Thalor and Ajin Cherian
Discussion: https://postgr.es/m/688b0b7f-2f6c-d827-c27b-216a8e3ea700@2ndquadrant.com
2020-09-03 04:24:07 +02:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2021-09-13 04:59:10 +02:00
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
|
2017-03-23 13:36:36 +01:00
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2017-01-19 18:00:00 +01:00
|
|
|
</variablelist>
|
|
|
|
</refsect1>
|
|
|
|
|
2017-02-08 03:26:50 +01:00
|
|
|
<refsect1>
|
|
|
|
<title>Notes</title>
|
|
|
|
|
|
|
|
<para>
|
2017-11-23 15:39:47 +01:00
|
|
|
See <xref linkend="logical-replication-security"/> for details on
|
2017-02-08 03:26:50 +01:00
|
|
|
how to configure access control between the subscription and the
|
|
|
|
publication instance.
|
|
|
|
</para>
|
2017-06-09 23:11:46 +02:00
|
|
|
|
2017-09-22 21:01:13 +02:00
|
|
|
<para>
|
|
|
|
When creating a replication slot (the default behavior), <command>CREATE
|
|
|
|
SUBSCRIPTION</command> cannot be executed inside a transaction block.
|
|
|
|
</para>
|
|
|
|
|
2017-06-09 23:11:46 +02:00
|
|
|
<para>
|
|
|
|
Creating a subscription that connects to the same database cluster (for
|
|
|
|
example, to replicate between databases in the same cluster or to replicate
|
|
|
|
within the same database) will only succeed if the replication slot is not
|
|
|
|
created as part of the same command. Otherwise, the <command>CREATE
|
|
|
|
SUBSCRIPTION</command> call will hang. To make this work, create the
|
|
|
|
replication slot separately (using the
|
|
|
|
function <function>pg_create_logical_replication_slot</function> with the
|
|
|
|
plugin name <literal>pgoutput</literal>) and create the subscription using
|
|
|
|
the parameter <literal>create_slot = false</literal>. This is an
|
|
|
|
implementation restriction that might be lifted in a future release.
|
|
|
|
</para>
|
2017-02-08 03:26:50 +01:00
|
|
|
</refsect1>
|
|
|
|
|
2017-01-19 18:00:00 +01:00
|
|
|
<refsect1>
|
|
|
|
<title>Examples</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Create a subscription to a remote server that replicates tables in
|
2017-02-18 00:59:29 +01:00
|
|
|
the publications <literal>mypublication</literal> and
|
2017-01-19 18:00:00 +01:00
|
|
|
<literal>insert_only</literal> and starts replicating immediately on
|
|
|
|
commit:
|
|
|
|
<programlisting>
|
|
|
|
CREATE SUBSCRIPTION mysub
|
2017-02-08 03:26:50 +01:00
|
|
|
CONNECTION 'host=192.168.1.50 port=5432 user=foo dbname=foodb'
|
2017-01-19 18:00:00 +01:00
|
|
|
PUBLICATION mypublication, insert_only;
|
|
|
|
</programlisting>
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
Create a subscription to a remote server that replicates tables in
|
|
|
|
the <literal>insert_only</literal> publication and does not start replicating
|
|
|
|
until enabled at a later time.
|
|
|
|
<programlisting>
|
|
|
|
CREATE SUBSCRIPTION mysub
|
2017-02-08 03:26:50 +01:00
|
|
|
CONNECTION 'host=192.168.1.50 port=5432 user=foo dbname=foodb'
|
2017-01-19 18:00:00 +01:00
|
|
|
PUBLICATION insert_only
|
2017-05-12 14:57:01 +02:00
|
|
|
WITH (enabled = false);
|
2017-06-14 19:55:43 +02:00
|
|
|
</programlisting></para>
|
2017-01-19 18:00:00 +01:00
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Compatibility</title>
|
|
|
|
|
|
|
|
<para>
|
2017-10-09 03:44:17 +02:00
|
|
|
<command>CREATE SUBSCRIPTION</command> is a <productname>PostgreSQL</productname>
|
2017-01-19 18:00:00 +01:00
|
|
|
extension.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
2017-11-23 15:39:47 +01:00
|
|
|
<member><xref linkend="sql-altersubscription"/></member>
|
|
|
|
<member><xref linkend="sql-dropsubscription"/></member>
|
|
|
|
<member><xref linkend="sql-createpublication"/></member>
|
|
|
|
<member><xref linkend="sql-alterpublication"/></member>
|
2017-01-19 18:00:00 +01:00
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
|
|
|
</refentry>
|