Movatterモバイル変換

Specifies whether theCREATE SUBSCRIPTION command should connect to the publisher at all. The default istrue. Setting this tofalse will force the values ofcreate_slot,enabled andcopy_data tofalse. (You cannot combine settingconnect tofalse with settingcreate_slot,enabled, orcopy_data totrue.)

Since no connection is made when this option isfalse, no tables are subscribed, and so after you enable the subscription nothing will be replicated. You will need to then runALTER SUBSCRIPTION ... REFRESH PUBLICATION for tables to be subscribed.

Specifies whether the command should create the replication slot on the publisher. The default istrue. If set tofalse, you are responsible for creating the publisher's slot in some other way.

Specifies whether the subscription should be actively replicating or whether it should just be set up but not started yet. The default istrue.

Name of the publisher's replication slot to use. The default is to use the name of the subscription for the slot name.

Settingslot_name toNONE means there will be no replication slot associated with the subscription. Use this when you will be creating the replication slot later manually. Such subscriptions must also have bothenabled andcreate_slot set tofalse.

Specifies whether the subscription will request the publisher to send the data in binary format (as opposed to text). The default isfalse. Even when this option is enabled, only data types having binary send and receive functions will be transferred in binary.

When doing cross-version replication, it could be that the publisher has a binary send function for some data type, but the subscriber lacks a binary receive function for that type. In such a case, data transfer will fail, and thebinary option cannot be used.

Specifies whether to copy pre-existing data in the publications that are being subscribed to when the replication starts. The default istrue.

If the publications containWHERE clauses, it will affect what data is copied. Refer to theNotes for details.

Specifies whether to enable streaming of in-progress transactions for this subscription. By default, all transactions are fully decoded on the publisher and only then sent to the subscriber as a whole.

The value of this parameter overrides thesynchronous_commit setting within this subscription's apply worker processes. The default value isoff.

It is safe to useoff for logical replication: If the subscriber loses transactions because of missing synchronization, the data will be sent again from the publisher.

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 settingsynchronous_commit for the subscriber tooff when the subscription is used for synchronous replication might increase the latency forCOMMIT on the publisher. In this scenario, it can be advantageous to setsynchronous_commit tolocal or higher.

Specifies whether two-phase commit is enabled for this subscription. The default isfalse.

When two-phase commit is enabled, prepared transactions are sent to the subscriber at the time ofPREPARE TRANSACTION, and are processed as two-phase transactions on the subscriber too. Otherwise, prepared transactions are sent to the subscriber only when committed, and are then processed immediately by the subscriber.

The implementation of two-phase commit requires that replication has successfully finished the initial table synchronization phase. So even whentwo_phase is enabled for a subscription, the internal two-phase state remains temporarily“pending” until the initialization phase completes. See columnsubtwophasestate ofpg_subscription to know the actual two-phase state.

Specifies whether the subscription should be automatically disabled if any errors are detected by subscription workers during data replication from the publisher. The default isfalse.