From 829fb5dfbf2343e27d52797776713345c71562f3 Mon Sep 17 00:00:00 2001 From: Peter Smith Date: Mon, 9 Aug 2021 12:28:39 +1000 Subject: [PATCH v2] create subscription options list order. Change the WITH subscription parameter to be properly alphaetically ordered. Otherwise it not very user-friending when looking for the option your are interested in. Currently it is mostly, but not fully alphabetical, so it looks like it was always supposed to ordered but has evolved to be muddled. --- doc/src/sgml/ref/create_subscription.sgml | 124 +++++++++++++++--------------- 1 file changed, 63 insertions(+), 61 deletions(-) diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml index 702934e..96a971d 100644 --- a/doc/src/sgml/ref/create_subscription.sgml +++ b/doc/src/sgml/ref/create_subscription.sgml @@ -96,6 +96,57 @@ CREATE SUBSCRIPTION subscription_name + + + binary (boolean) + + + Specifies whether the subscription will request the publisher to + send the data in binary format (as opposed to text). + The default is false. + Even when this option is enabled, only data types that have + binary send and receive functions will be transferred in binary. + + + + 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 binary option cannot be used. + + + + + + connect (boolean) + + + Specifies whether the CREATE SUBSCRIPTION + should connect to the publisher at all. Setting this to + false will change default values of + enabled, create_slot and + copy_data to false. + + + + It is not allowed to combine connect set to + false and enabled, + create_slot, or copy_data + set to true. + + + + Since no connection is made when this option is set + to false, the tables are not subscribed, and so + after you enable the subscription nothing will be replicated. + It is required to run + ALTER SUBSCRIPTION ... REFRESH PUBLICATION in order + for tables to be subscribed. + + + + copy_data (boolean) @@ -148,6 +199,18 @@ CREATE SUBSCRIPTION subscription_name + streaming (boolean) + + + 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. + + + + + synchronous_commit (enum) @@ -180,67 +243,6 @@ CREATE SUBSCRIPTION subscription_name - binary (boolean) - - - Specifies whether the subscription will request the publisher to - send the data in binary format (as opposed to text). - The default is false. - Even when this option is enabled, only data types that have - binary send and receive functions will be transferred in binary. - - - - 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 binary option cannot be used. - - - - - - connect (boolean) - - - Specifies whether the CREATE SUBSCRIPTION - should connect to the publisher at all. Setting this to - false will change default values of - enabled, create_slot and - copy_data to false. - - - - It is not allowed to combine connect set to - false and enabled, - create_slot, or copy_data - set to true. - - - - Since no connection is made when this option is set - to false, the tables are not subscribed, and so - after you enable the subscription nothing will be replicated. - It is required to run - ALTER SUBSCRIPTION ... REFRESH PUBLICATION in order - for tables to be subscribed. - - - - - streaming (boolean) - - - 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. - - - - - two_phase (boolean) -- 1.8.3.1