From 061e22c92cd8b224b716d9e8dd9064b9b98f81d6 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 16 Sep 2022 13:04:45 -0400 Subject: [PATCH] PGD: soften language against using legacy options --- product_docs/docs/pgd/4/bdr/durability.mdx | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/pgd/4/bdr/durability.mdx b/product_docs/docs/pgd/4/bdr/durability.mdx index a3130b71629..77767abbb70 100644 --- a/product_docs/docs/pgd/4/bdr/durability.mdx +++ b/product_docs/docs/pgd/4/bdr/durability.mdx @@ -45,9 +45,7 @@ Postgres provides [Physical Streaming Replication](https://www.postgresql.org/do For backward compatibility, BDR still supports configuring synchronous replication with `synchronous_commit` and `synchronous_standby_names`. See [Legacy synchronous replication](durability#legacy-synchronous-replication-using-bdr), -but the use of [Group Commit](group-commit) is recommended instead -in all cases. - +but consider using [Group Commit](group-commit) instead. ## Terms and definitions BDR nodes can take different @@ -108,7 +106,7 @@ Postgres crashes.* `synchronous_replication_availability` to `async'`, otherwise the values for the asynchronous BDR default apply.* -*(3) Not recommended. Consider using Group Commit instead.* +*(3) Consider using Group Commit instead.* Reception ensures the peer operating normally can eventually apply the transaction without requiring any further @@ -208,8 +206,7 @@ required synchronization level and prevents loss of data. ## Legacy synchronous replication using BDR !!! Note - We don't recommend this approach. Consider using - [Group Commit](group-commit) instead. + Consider using [Group Commit](group-commit) instead. ### Usage