From: Petr Jelinek Date: Sun, 22 Mar 2015 22:26:14 +0000 (+0100) Subject: bdr: doc: More detailed docs for bdr.bdr_subscribe(). X-Git-Tag: bdr-plugin/0.9.0~31 X-Git-Url: http://git.postgresql.org/gitweb/static/session/%7B%7Bsession.id%7D%7D-%7B%7Bsession.title%7Cslugify%7D%7D?a=commitdiff_plain;h=61e2b6f7a526329167ac5a84f9b75de5d1bf2c0b;p=2ndquadrant_bdr.git bdr: doc: More detailed docs for bdr.bdr_subscribe(). --- diff --git a/doc/manual-functions.sgml b/doc/manual-functions.sgml index 6bcb5dac4e..9b4bf98560 100644 --- a/doc/manual-functions.sgml +++ b/doc/manual-functions.sgml @@ -28,10 +28,10 @@ bdr.bdr_subscribe - bdr.bdr_subscribe(local_node_name, subscribe_to_dsn, node_local_dsn, apply_delay integer DEFAULT NULL, replication_sets text[] DEFAULT ARRAY['default']) + bdr.bdr_subscribe(local_node_name, subscribe_to_dsn, node_local_dsn, apply_delay integer DEFAULT NULL, replication_sets text[] DEFAULT ARRAY['default']), synchronize bdr_sync_type DEFAULT 'full' void - Subscribes to changes made on another node + Subscribes to changes made on another node. See . @@ -96,8 +96,90 @@ - + + + <function>bdr.bdr_subscribe</function> + + + subscribe + + + + The function bdr.bdr_subscribe will create unidirectional + connection between the local node and subscribe_to_dsn node. + + + + The parameters are: + + + local_node_name + + + A string specifying the name of the new node (for identification + purposes). + + + + + + subscribe_to_dsn + + + Connection string of the remote node from which replication should be + started. + + + + + + node_local_dsn + + + Public connection string to the new local node. It is + used during initialization. + + + + + + apply_delay (optional) + + + Time (in milliseconds), the node will wait before applying changes + incoming from from the remote node. + + + + + + replication_sets (optional) + + + Text array of replication sets which should be replicated to the local + node. Note that you need to assign individual tables to the + replication sets on the remote node. + + + + + + synchronize (optional) + + + What to synchronize (copy) during the node initialization. Currently + supported values are full (the default) which means do + full schema and data copy and none which means don't copy + anything. Note that this can cause apply failures if the schemas of + nodes differ. + + + + + + +