Merge pull request #3707 from EnterpriseDB/release/2023-02-21a

Release: 2023-02-21a
EnterpriseDB · Feb 21, 2023 · 7af8ba5 · 7af8ba5 · github-actions · Feb 21, 2023
2 parents 96b447c + 215470d
commit 7af8ba5
Show file tree

Hide file tree

Showing 24 changed files with 49 additions and 587 deletions.
diff --git a/product_docs/docs/pgd/4/bdr/nodes.mdx b/product_docs/docs/pgd/4/bdr/nodes.mdx
@@ -936,7 +936,7 @@ bdr.create_node_group(node_group_name text,
      `read coordinator`, and `write coordinator`. `subscriber-only` type is
      used to create a group of nodes that receive changes only from the
      fully joined nodes in the cluster, but they never send replication
-     changes to other nodes. See [Subscriber-only nodes](#subscriber-only-nodes) for more details.
+     changes to other nodes. See [Subscriber-only groups](#subscriber-only-groups) for more details.
      `Datanode` implies that the group represents a shard, whereas the other
      values imply that the group represents respective coordinators.
      Except `subscriber-only`, the other values are reserved for future use.

diff --git a/product_docs/docs/pgd/5/appusage.mdx b/product_docs/docs/pgd/5/appusage.mdx
@@ -1,7 +1,7 @@
 ---
 title: Application use
 redirects: 
-  - bdr/appusage
+  - ../bdr/appusage
 ---
 
 Learn about the BDR application from a user perspective.

diff --git a/product_docs/docs/pgd/5/catalogs.mdx b/product_docs/docs/pgd/5/catalogs.mdx
@@ -1,7 +1,7 @@
 ---
 title: Catalogs and views
 redirects: 
-  - bdr/catalogs
+  - ../bdr/catalogs
 
 ---
 Catalogs and views are presented here in alphabetical order.
@@ -220,7 +220,7 @@ A view containing active global locks on this node. The [`bdr.global_locks`](#bd
 exposes BDR's shared-memory lock state tracking, giving administrators greater
 insight into BDR's global locking activity and progress.
 
-See [Monitoring global locks](monitoring#monitoring-global-locks)
+See [Monitoring global locks](monitoring/sql#monitoring-global-locks)
 for more information about global locking.
 
 #### `bdr.global_locks` columns
@@ -548,7 +548,7 @@ given node.
 This view contains information about replication slots used in the current
 database by BDR.
 
-See [Monitoring outgoing replication](monitoring#monitoring-outgoing-replication)
+See [Monitoring outgoing replication](monitoring/sql#monitoring-outgoing-replication)
 for guidance on the use and interpretation of this view's fields.
 
 #### `bdr.node_slots` columns
@@ -1282,7 +1282,7 @@ node. Specifically, it tracks:
 * Node joins (to the cluster)
 * Raft state changes (i.e. whenever the node changes its role in the consensus
 protocol - leader, follower or candidate to leader) - see [Monitoring Raft Consensus](monitoring/sql#monitoring-raft-consensus)
-* Whenever a worker has errored out (see [bdr.workers](#bdr.workers)
+* Whenever a worker has errored out (see [bdr.workers](#bdrworkers)
 and [Monitoring BDR Replication Workers](monitoring/sql#monitoring-bdr-replication-workers))
 
 | Name           | Type        | Description                                                                         |

diff --git a/product_docs/docs/pgd/5/configuration.mdx b/product_docs/docs/pgd/5/configuration.mdx
@@ -2,7 +2,7 @@
 navTitle: Postgres configuration
 title: Postgres configuration 
 redirects: 
-  - bdr/configuration
+  - ../bdr/configuration
 
 ---
 

diff --git a/product_docs/docs/pgd/5/ddl.mdx b/product_docs/docs/pgd/5/ddl.mdx
@@ -1,7 +1,7 @@
 ---
 title: DDL replication
 redirects: 
-  - bdr/ddl
+  - ../bdr/ddl
 
 ---
 

diff --git a/product_docs/docs/pgd/5/durability/index.mdx b/product_docs/docs/pgd/5/durability/index.mdx
@@ -55,7 +55,7 @@ Postgres provides [Physical Streaming Replication](https://www.postgresql.org/do
 (PSR), which is unidirectional but offers a [synchronous variant](https://www.postgresql.org/docs/current/warm-standby.html#SYNCHRONOUS-REPLICATION).
 For backward compatibility, BDR still supports configuring synchronous
 replication with `synchronous_commit` and `synchronous_standby_names`. See
-[Legacy synchronous replication](#legacy-synchronous-replication-using-pgd),
+[Legacy synchronous replication](#legacy-synchronous-replication-using-bdr),
 but consider using [Group Commit](group-commit) instead.
 
 ## Terms and definitions

diff --git a/product_docs/docs/pgd/5/functions.mdx b/product_docs/docs/pgd/5/functions.mdx
@@ -2,7 +2,7 @@
 navTitle: System functions
 title: System functions
 redirects: 
-  - bdr/functions
+  - ../bdr/functions
 ---
 
 Perform BDR management primarily by using functions you call from SQL.
@@ -707,7 +707,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/sql/#monitoring-bdr-versions).
 
 This function calls `bdr.run_on_all_nodes()`.
 
@@ -731,7 +731,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/sql/#monitoring-raft-consensus).
 
 This function calls `bdr.run_on_all_nodes()`.
 
@@ -751,7 +751,7 @@ bdr.monitor_local_replslots()
 #### Notes
 
 This function returns a record with fields `status` and `message`,
-as explained in [Monitoring replication slots](monitoring/#monitoring-replication-slots).
+as explained in [Monitoring replication slots](monitoring/sql/#monitoring-replication-slots).
 
 ### bdr.wal_sender_stats
 
@@ -801,7 +801,7 @@ bdr.get_decoding_worker_stat()
 
 #### Notes
 
-For further details, see [Monitoring WAL senders using LCR](monitoring/#monitoring-wal-senders-using-lcr).
+For further details, see [Monitoring WAL senders using LCR](monitoring/sql/#monitoring-wal-senders-using-lcr).
 
 ### bdr.lag_control
 

diff --git a/product_docs/docs/pgd/5/nodes.mdx b/product_docs/docs/pgd/5/nodes.mdx
@@ -1,7 +1,7 @@
 ---
 title: Node management
 redirects: 
-  - bdr/nodes
+  - ../bdr/nodes
 
 ---
 
@@ -941,7 +941,7 @@ bdr.create_node_group(node_group_name text,
      `read coordinator`, and `write coordinator`. `subscriber-only` type is
      used to create a group of nodes that receive changes only from the
      fully joined nodes in the cluster, but they never send replication
-     changes to other nodes. See [Subscriber-only nodes](#subscriber-only-nodes) for more details.
+     changes to other nodes. See [Subscriber-only groups](#subscriber-only-groups) for more details.
      `Datanode` implies that the group represents a shard, whereas the other
      values imply that the group represents respective coordinators.
      Except `subscriber-only`, the other values are reserved for future use.
@@ -1023,7 +1023,7 @@ bdr.alter_node_group_config(node_group_name text,
      initially the `local` commit scope. This applies only to the
      top-level node group. You can use individual rules for different
      origin groups of the same commit scope. See
-     [Origin groups](durability/group-commit/#origin-groups) for more details.
+     [Origin groups](durability/commit-scopes/#origin-groups) for more details.
 
 #### Notes