From 76f48ca964442c55cb7c6f2add0b817a402cb4cb Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 11 Jul 2023 11:11:00 +0100 Subject: [PATCH] Move tables into legacy sync Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/index.mdx | 16 ++-------------- .../docs/pgd/5/durability/legacy-sync.mdx | 16 ++++++++++++++++ 2 files changed, 18 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/index.mdx b/product_docs/docs/pgd/5/durability/index.mdx index b8db0774e25..515d20ae432 100644 --- a/product_docs/docs/pgd/5/durability/index.mdx +++ b/product_docs/docs/pgd/5/durability/index.mdx @@ -54,10 +54,12 @@ Commit scopes allow two ways of controlling durability of the transaction: be in terms of replication before allowing commit to proceed. +!!! Note Legacy synchronization availability For backward compatibility, PGD still supports configuring synchronous replication with `synchronous_commit` and `synchronous_standby_names`. See [Legacy synchronous replication](legacy-sync) for more on this option, but consider using [Group Commit](group-commit) instead. +!!! ## Terms and definitions @@ -163,7 +165,6 @@ The following table summarizes the differences. | Variant | Order of apply vs persist | Replication before or after commit | |:-----------------|:-------------------------:|:----------------------------------:| -| PSR | persist first | after WAL flush of commit record | | PGD Async | apply first | after WAL flush of commit record | | PGD Lag Control | apply first | after WAL flush of commit record | | PGD Group Commit | apply first | before COMMIT on origin | @@ -214,19 +215,6 @@ the `bdr.commit_scope` configuration parameter. For full details of the commit scope language with all the options described, see [Commit scopes](commit-scopes). -### Postgres configuration parameters - -The following table provides an overview of the configuration -settings that you must set to a non-default value (req) and those that are -optional (opt) but affecting a specific variant. - -| Setting (GUC) | Group Commit | Lag Control | PSR (1) | Legacy Sync | -|--------------------------------------|:------------:|:-----------:|:-------:|:-----------:| -| synchronous_standby_names | n/a | n/a | req | req | -| synchronous_commit | n/a | n/a | opt | opt | -| synchronous_replication_availability | n/a | n/a | opt | opt | -| bdr.commit_scope | opt | opt | n/a | n/a | - ## Planned shutdown and restarts When using Group Commit with receive confirmations, take care diff --git a/product_docs/docs/pgd/5/durability/legacy-sync.mdx b/product_docs/docs/pgd/5/durability/legacy-sync.mdx index f4eb2911012..0f3e707ddcf 100644 --- a/product_docs/docs/pgd/5/durability/legacy-sync.mdx +++ b/product_docs/docs/pgd/5/durability/legacy-sync.mdx @@ -17,6 +17,10 @@ replication with `synchronous_commit` and `synchronous_standby_names`. See [Legacy synchronous replication](#legacy-synchronous-replication-using-pgd), but consider using [Group Commit](group-commit) instead. +Unlike PGD replication options, PSR sync will persist first, replicating after the WAL flush of commit record. + + + ### Usage To enable synchronous replication using PGD, you need to add the application @@ -60,6 +64,18 @@ values for the asynchronous PGD default apply.* *(3) Written to the OS, durable if the OS remains running and only Postgres crashes.* +### Postgres configuration parameters + +The following table provides an overview of the configuration +settings that you must set to a non-default value (req) and those that are +optional (opt) but affecting a specific variant. + +| Setting (GUC) | Group Commit | Lag Control | PSR | Legacy Sync | +|--------------------------------------|:------------:|:-----------:|:-------:|:-----------:| +| synchronous_standby_names | n/a | n/a | req | req | +| synchronous_commit | n/a | n/a | opt | opt | +| synchronous_replication_availability | n/a | n/a | opt | opt | + ### Migration to commit scopes You configure the Group Commit feature of PGD independent of