Merge pull request #3170 from EnterpriseDB/release/2022-09-18

Release: 2022-09-18
EnterpriseDB · Sep 18, 2022 · 7f2beab · 7f2beab
2 parents 76abb21 + 3e6c670
commit 7f2beab
Show file tree

Hide file tree

Showing 9 changed files with 326 additions and 230 deletions.
diff --git a/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx b/product_docs/docs/biganimal/release/using_cluster/01_postgres_access.mdx
@@ -2,7 +2,7 @@
 title: "Managing Postgres access"
 ---
 
-Don't use the `edb_admin` database role and `edb_admin` database created when creating your cluster in your application. Instead, create a new database role and a new database, which provides a high level of isolation in Postgres. If multiple applications are using the same cluster, each database can also contain multiple schemas, essentially a namespace in the database. If strict isolation is needed, use a dedicated cluster or dedicated database. If that strict isolation level isn't required, a you can deploy a single database with multiple schemas. Refer to [Privileges](https://www.postgresql.org/docs/current/ddl-priv.html) in the PostgreSQL documentation to further customize ownership and roles to your requirements.
+Don't use the `edb_admin` database role and `edb_admin` database created when creating your cluster in your application. Instead, create a new database role and a new database, which provides a high level of isolation in Postgres. If multiple applications are using the same cluster, each database can also contain multiple schemas, essentially a namespace in the database. If strict isolation is needed, use a dedicated cluster or dedicated database. If that strict isolation level isn't required, you can deploy a single database with multiple schemas. Refer to [Privileges](https://www.postgresql.org/docs/current/ddl-priv.html) in the PostgreSQL documentation to further customize ownership and roles to your requirements.
 
 To create a new role and database, first connect using `psql`:
 
@@ -12,7 +12,7 @@ psql -W "postgres://[email protected]:5432/edb_admin?sslmod
 
 ## Notes on the edb_admin role
 
-- The `edb_admin` role does not have superuser priviledges by default. Contact [Support](../overview/support) to request superuser priviledges for `edb_admin`. If you request superuser privileges, you **must** take care to limit the number of connections used by superusers to avoid degraded service and/or compromising availability.
+- The `edb_admin` role does not have superuser privileges by default. Contact [Support](../overview/support) to request superuser priviledges for `edb_admin`. If you request superuser privileges, you **must** take care to limit the number of connections used by superusers to avoid degraded service and/or compromising availability.
 
 - Changes to system configuration (GUCs) made by edb_admin or other Postgres users are not persisted though a reboot or maintenance. Use the BigAnimal portal to modify system configuration.
 

diff --git a/...ocs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx b/...ocs/biganimal/release/using_cluster/05_monitoring_and_logging/metrics/index.mdx
diff --git 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
 

diff --git a/product_docs/docs/pgd/4/bdr/functions.mdx b/product_docs/docs/pgd/4/bdr/functions.mdx
@@ -705,7 +705,7 @@ bdr.monitor_group_versions()
 #### Notes
 
 This function returns a record with fields `status` and `message`,
-as explained in [Monitoring](../../monitoring/#monitoring-bdr-versions).
+as explained in [Monitoring](../monitoring/#monitoring-bdr-versions).
 
 This function calls `bdr.run_on_all_nodes()`.
 
@@ -724,7 +724,7 @@ bdr.monitor_group_raft()
 #### Notes
 
 This function returns a record with fields `status` and `message`,
-as explained in [Monitoring](../../monitoring/#monitoring-raft-consensus).
+as explained in [Monitoring](../monitoring/#monitoring-raft-consensus).
 
 This function calls `bdr.run_on_all_nodes()`.
 

diff --git a/product_docs/docs/pgd/4/bdr/index.mdx b/product_docs/docs/pgd/4/bdr/index.mdx
@@ -159,7 +159,7 @@ overhead of replication as the cluster grows and minimizing the bandwidth to oth
 
 BDR is compatible with Postgres, EDB Postgres Extended Server, and EDB Postgres
 Advanced Server distributions and can be deployed as a
-standard Postgres extension. See [Compatibility matrix](/pgd/latest/compatibility_matrix/)
+standard Postgres extension. See [Compatibility matrix](/pgd/latest/#compatibility-matrix)
 for details of supported version combinations.
 
 Some key BDR features depend on certain core

diff --git a/product_docs/docs/pgd/4/bdr/transaction-streaming.mdx b/product_docs/docs/pgd/4/bdr/transaction-streaming.mdx
@@ -117,7 +117,7 @@ either a writer or a file. The decision is based on several factors:
     (writer 0 is always reserved for non-streamed transactions.)
 -   If parallel apply is on but all writers are already busy handling streamed
     transactions, then the new transaction is streamed to a file. See
-    [bdr.writers](../../monitoring#monitoring-bdr-writers) to check BDR
+    [bdr.writers](../monitoring#monitoring-bdr-writers) to check BDR
     writer status.
 
 If streaming to a writer is possible (that is, a free writer is available), then the

diff --git a/product_docs/docs/pgd/4/cli/installing_cli.mdx b/product_docs/docs/pgd/4/cli/installing_cli.mdx
@@ -43,5 +43,5 @@ The `pgd-config.yml`, is located in the `/etc/edb` directory, by default. The PG
   2. `$HOME/.edb`
   3. `.` (working directory)
 
-If you rename the file or move it to another location, specify the new name and location using the optional `-f` or `--config-file` flag when entering a command. See the [sample use case](/pgd_cli/using_cli/#passing-a-database-connection-string-directly-to-a-command).
+If you rename the file or move it to another location, specify the new name and location using the optional `-f` or `--config-file` flag when entering a command. See the [sample use case](/pgd/latest/cli/#passing-a-database-connection-string).
 
diff --git a/product_docs/docs/pgd/4/overview/index.mdx b/product_docs/docs/pgd/4/overview/index.mdx
@@ -21,17 +21,17 @@ Three different Postgres distributions can be used:
 What Postgres distribution and version is right for you depends on the features you need.
 See the feature matrix in [Choosing a Postgres distribution](/pgd/latest/choosing_server) for detailed comparison.
 
-## [BDR](bdr)
+## [BDR](../bdr)
 
-A Postgres server with the [BDR](bdr) extension installed is referred to as a BDR
+A Postgres server with the [BDR](../bdr) extension installed is referred to as a BDR
 node. BDR nodes can be either data nodes or witness nodes.
 
 Witness nodes don't participate in data replication and are only used as a
 tie-breaker for consensus.
 
-## [HARP](harp)
+## [HARP](../harp)
 
-[HARP](harp) is connection management tool for a EDB Postgres Distributed cluster.
+[HARP](../harp) is connection management tool for a EDB Postgres Distributed cluster.
 
 It leverages consensus-driven quorum to determine the correct connection end-point
 in a semi-exclusive manner to prevent unintended multi-node writes from an

diff --git a/static/_redirects b/static/_redirects
@@ -38,13 +38,13 @@
 # PGD
 /docs/pgd/latest/overview/bdr/*        /docs/pgd/latest/bdr/:splat  302
 /docs/pgd/latest/overview/harp/*       /docs/pgd/latest/harp/:splat  302
-/docs/bdr/latest/*        /docs/pgd/latest/overview/bdr/:splat  302
-/docs/bdr/4/*             /docs/pgd/4/overview/bdr/:splat       301
+/docs/bdr/latest/*        /docs/pgd/latest/bdr/:splat  302
+/docs/bdr/4/*             /docs/pgd/4/bdr/:splat       301
 /docs/bdr/3.7/*           /docs/pgd/3.7/bdr/:splat              301
 /docs/bdr/3.6/*           /docs/pgd/3.6/                        302
 /docs/pgd/3.6/pglogical/* /docs/pgd/3.6/                        302
-/docs/harp/latest/*       /docs/pgd/latest/overview/harp/:splat 302
-/docs/harp/2/*            /docs/pgd/4/overview/harp/:splat      301
+/docs/harp/latest/*       /docs/pgd/latest/harp/:splat 302
+/docs/harp/2/*            /docs/pgd/4/harp/:splat               301
 /docs/pglogical/latest/*  /docs/pgd/3.7/pglogical/:splat        302
 
 # BART