You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: product_docs/docs/pgd/6/nodes/logical_standby_nodes.mdx
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,14 @@ A master node can have zero, one, or more logical standby nodes.
14
14
location is always preferred.
15
15
16
16
Logical standby nodes are nodes that are held in a state of continual recovery,
17
-
constantly updating until they're required. This behavior is similar to how Postgres physical standbys operate while using logical replication for better performance. [`bdr.join_node_group`](/pgd/latest/reference/nodes-management-interfaces#bdrjoin_node_group) has the `pause_in_standby`
18
-
option to make the node stay in halfway-joined as a logical standby node.
17
+
constantly updating until they're required. This behavior is similar to how Postgres physical
18
+
standbys operate, while using logical replication for better performance.
19
19
Logical standby nodes receive changes but don't send changes made locally
20
20
to other nodes.
21
21
22
+
A logical standby is created by specifying the `node_kind` as `standby` when creating
23
+
the node with [`bdr.create_node`](/pgd/latest/reference/nodes-management-interfaces#bdrpromote_node).
Copy file name to clipboardExpand all lines: product_docs/docs/pgd/6/reference/nodes-management-interfaces.mdx
+1-8Lines changed: 1 addition & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -294,7 +294,6 @@ Joins the local node to an already existing PGD group.
294
294
bdr.join_node_group (
295
295
join_target_dsn text,
296
296
node_group_name text DEFAULT NULL,
297
-
pause_in_standby boolean DEFAULT NULL,
298
297
wait_for_completion boolean DEFAULT true,
299
298
synchronize_structure text DEFAULT 'all'
300
299
)
@@ -308,19 +307,13 @@ bdr.join_node_group (
308
307
|`node_group_name`| Optional name of the PGD group. Defaults to NULL, which tries to detect the group name from information present on the source node. |
309
308
|`wait_for_completion`| Wait for the join process to complete before returning. Defaults to `true`. |
310
309
|`synchronize_structure`| Specifies whether to perform database structure (schema) synchronization during the join. `all`, the default setting, synchronizes the complete database structure. `none` does not synchronize any structure. However, data will still be synchronized, meaning the database structure must already be present on the joining node. Note that by design, neither schema nor data will ever be synchronized to witness nodes. |
311
-
|`pause_in_standby`| Optionally tells the join process to join only as a logical standby node, which can be later promoted to a full member. This option is deprecated and will be disabled or removed in future versions of PGD. |
312
-
313
-
!!! Warning
314
-
`pause_in_standby` is deprecated since BDR 5.0. The recommended way to create
315
-
a logical standby is to set `node_kind` to `standby` when creating the node
316
-
with [`bdr.create_node`](#bdrcreate_node).
317
310
318
311
If `wait_for_completion` is specified as `false`, the function call returns
319
312
as soon as the joining procedure starts. You can see the progress of the join in
320
313
the log files and the [`bdr.event_summary`](/pgd/latest/reference/catalogs-internal#bdrevent_summary)
321
314
information view. You can call the function [`bdr.wait_for_join_completion()`](#bdrwait_for_join_completion)
322
315
after `bdr.join_node_group()` to wait for the join operation to complete.
323
-
It can emit progress information if called with `verbose_progress` set to `true`.
316
+
It can emit progress information if [`bdr.wait_for_join_completion()`](#bdrwait_for_join_completion) is called with `verbose_progress` set to `true`.
0 commit comments