From 0b2072d3c8f0cebd55ccfb3c3ddb8c9c248aa29b Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Tue, 23 Jan 2024 11:07:46 -0500 Subject: [PATCH 01/22] Edits to Big Animal PR5123 --- .../release/overview/05_database_version_policy.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx b/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx index 7bd74d9c124..ddaf0c6ad21 100644 --- a/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx +++ b/product_docs/docs/biganimal/release/overview/05_database_version_policy.mdx @@ -24,18 +24,18 @@ The only exception is customers who purchased Extended Life Support (ELS) prior ## Key dates -While PostgreSQL officially deprecates version 11 on November 9, 2023, BigAnimal will deprecate PostgreSQL 11 on November 20, 2023 in alignment with the broader EDB portfolio. +While PostgreSQL officially deprecated version 11 on November 9, 2023, BigAnimal deprecated PostgreSQL 11 on November 20, 2023 in alignment with the broader EDB portfolio. -On November 20, 2023, BigAnimal will deprecate support for PostgreSQL 11 and EDB Postgres Advanced Server 11 using the following schedule. We recommend that you take action and upgrade your Postgres databases running on major version 11 to a later version, such as PostgreSQL version 15. +On November 20, 2023, BigAnimal deprecated support for PostgreSQL 11 and EDB Postgres Advanced Server 11 using the following schedule. We recommend that you take action and upgrade your Postgres databases running on major version 11 to a later version, such as PostgreSQL version 15. -BigAnimal will automatically upgrade your Postgres 11 instances to a later version at the end of six months. Customers who purchased Extended Life Support are exempt. To purchase Extended Life Support, contact Sales. BigAnimal reserves the right to upgrade sooner in case of a security issue. +BigAnimal automatically upgrades your Postgres 11 instances to a later version at the end of six months. Customers who purchased Extended Life Support are exempt. To purchase Extended Life Support, contact Sales. BigAnimal reserves the right to upgrade sooner in case of a security issue. -| Action or Recommendation | Dates - Postgres 11 | Dates - Postgres 12 | +| Action or recommendation | Dates - Postgres 11 | Dates - Postgres 12 | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ------------------- | | BigAnimal no longer supports the Postgres version. | November 20, 2023 | December 9, 2024 | | The PostgreSQL community plans to deprecate the version and won't provide any security patches after this date. | November 9, 2023 | November 14, 2024 | | Start upgrading your BigAnimal instances to a later major version starting on this date. You can use pg_dump to restore your cluster into a later version. | Until May 20, 2023 | Until June 9, 2024 | -| You can't create a new instance with Postgres version in the BigAnimal interfaces after this date. | May 20, 2023 | June 9, 2024 | -| If you manually restore a cluster, you can't restore it with Postgres version after this date. You will need to restore that Postgres cluster into a newer version of Postgres. | May 20, 2023 | June 9, 2024 | +| You can't create a new instance with Postgres version 11 in the BigAnimal interfaces after this date. | May 20, 2023 | June 9, 2024 | +| If you manually restore a cluster, you can't restore it with Postgres version 11 after this date. You need to restore that Postgres cluster into a newer version of Postgres. | May 20, 2023 | June 9, 2024 | | BigAnimal will force a major version upgrade and won't allow any new clusters to be provisioned or restored to the old Postgres version. Only customers on Extended Life Support are exempt for the duration of their contract. If you don’t purchase Extended Life Support on this date, your clusters will be upgraded. | April 20, 2024 | May 9, 2025 | | Extended Life Support starts six months after PostgreSQL community deprecates the Postgres version. BigAnimal reserves the right to upgrade in case of a security issue. | April 20, 2024 | May 9, 2025 | From 615b4ad240f8f6146613bc96ccb8c7e72eabd559 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 2 Feb 2024 12:20:18 +0000 Subject: [PATCH 02/22] First pass changes Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 8 ++++++-- product_docs/docs/pgd/5/reference/commit-scopes.mdx | 10 +++++----- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index 6a50a091ef9..996a80ade67 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -93,8 +93,12 @@ conflict resolution works. Eager means that conflicts are resolved eagerly (as part of agreement on COMMIT), and conflicting transactions get aborted with a serialization error. This approach provides greater isolation than the asynchronous resolution at the -price of performance. For the details about how Eager conflict resolution works, -see [Eager conflict resolution](../consistency/eager). +price of performance. Eager resolution should only be used with an `ALL` commit +scope group, which in turn requires the GROUP COMMIT commit decision set to `raft`. + + +For the details about how Eager conflict resolution works, +see [Eager conflict resolution](../consistency/eager). ### Aborts diff --git a/product_docs/docs/pgd/5/reference/commit-scopes.mdx b/product_docs/docs/pgd/5/reference/commit-scopes.mdx index 4cb9545b41f..dc695c265ff 100644 --- a/product_docs/docs/pgd/5/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/reference/commit-scopes.mdx @@ -74,7 +74,9 @@ A transaction under this commit scope group will be considered committed if a ma Example: `ALL (left_dc)` -A transaction under this commit scope group will be considered committed if all of the nodes in the `left_dc` group confirm they processed the transaction. +A transaction under this commit scope group will be considered committed if all of the nodes in the `left_dc` group confirm they processed the transaction. + +When `ALL` is used with [`GROUP COMMIT`](#group-commit), the [`commit_decision`](#commit_decision-settings) setting must be set to `raft` to avoid reconciliation issues. ### ALL NOT @@ -147,7 +149,7 @@ When set to true, two-phase commit transactions: The value `async` means resolve conflicts asynchronously during replication using the conflict resolution policy. -The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. +The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. The `eager` conflict_resolution setting must only be used with the `ALL` commit scope group, and in turn must be used with a [`commit_decision`](#commit_decision-settings) set to `raft`. See ["Conflict resolution" in Group Commit](../durability/group-commit/#conflict-resolution). @@ -157,12 +159,10 @@ The value `group` means the preceding `commit_scope_group` specification also af The value `partner` means the partner node decides whether transactions can be committed. This value is allowed only on groups with 2 data nodes. -The value `raft` means the COMMIT decision is done using Raft consensus of all the nodes in the cluster, independent of any `commit_scope_group` consensus. This option has low performance and is for backward compatibility only. +The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. This option must be used when the `ALL` commit scope group is being used to ensure no divergence between the nodes over the decision. This option may have low performance. See ["Commit decisions" in Group Commit](../durability/group-commit/#commit-decisions). - - ## CAMO With the client's cooperation, enables protection to prevent multiple insertions of the same transaction in failover scenarios. From 50468d9b9530c04c7c453d69de3378fc3fc8cd9c Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Fri, 2 Feb 2024 12:20:45 -0500 Subject: [PATCH 03/22] edits to biganimal pr5131 --- .../release/getting_started/creating_a_cluster/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx index 8a47793ec79..14011943d2f 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx @@ -98,7 +98,7 @@ The following options aren't available when creating your cluster: 1. In the **Storage** section: - By default, the **Database Storage** volume stores the Postgres data and the Write-Ahead (WAL) Logs together. If you want to improve write performance for WAL files, you can allocate separate storage volume for the WAL files. To allocate separate storage volume for WAL files, select the check-box before **Use a separate storage volume for Write-Ahead Logs**. Then select the Volume Type, Size, IOPS, and Disk Throughput separately for **Database Storage** and **Write-Ahead Logs Storage**. If you allocate separate storage volume for the WAL files, you have to pay cloud infrastructure costs for the second volume. Once separate storage volume is allocated for WAL files, it can't be removed from the cluster settings later on. + By default, the **Database Storage** volume stores the Postgres data and the write-ahead logs (WAL) together. If you want to improve write performance for WAL files, you can allocate separate storage volume for the WAL files. To allocate separate storage volume for WAL files, select **Use a separate storage volume for Write-Ahead Logs**. Then select the volume type, size, IOPS, and disk throughput separately for **Database Storage** and **Write-Ahead Logs Storage**. If you allocate separate storage volume for the WAL files, you have to pay cloud infrastructure costs for the second volume. Once separate storage volume is allocated for WAL files, you can't remove it from the cluster settings later on. From the **Volume Type** list, select your volume type. From bbaaa3ee506f0a9f4dcaa962b34ef93af5db4de6 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Tue, 6 Feb 2024 10:58:57 -0500 Subject: [PATCH 04/22] Edits to PGD pr5209 --- .../docs/pgd/5/reference/nodes-management-interfaces.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx b/product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx index 7310420d819..faf2946c870 100644 --- a/product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx +++ b/product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx @@ -246,8 +246,8 @@ bdr.create_node(node_name text, database. Valid node names consist of lowercase letters, numbers, hyphens, and underscores. - `local_dsn` — Connection string to the node. -- `node_kind` — One of `data` (the default), `standby`, `subscriber-only` - or `witness`. If this parameter is not set, or `NULL` is provided, +- `node_kind` — One of `data` (the default), `standby`, `subscriber-only`, + or `witness`. If you don't set this parameter, or if you provide `NULL`, the default `data` node kind is used. ### Notes From 4cb284eaf2ff49f93537c98ccc591792c5f78296 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 2 Feb 2024 12:20:18 +0000 Subject: [PATCH 05/22] First pass changes Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 8 ++++++-- product_docs/docs/pgd/5/reference/commit-scopes.mdx | 10 +++++----- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index 6a50a091ef9..996a80ade67 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -93,8 +93,12 @@ conflict resolution works. Eager means that conflicts are resolved eagerly (as part of agreement on COMMIT), and conflicting transactions get aborted with a serialization error. This approach provides greater isolation than the asynchronous resolution at the -price of performance. For the details about how Eager conflict resolution works, -see [Eager conflict resolution](../consistency/eager). +price of performance. Eager resolution should only be used with an `ALL` commit +scope group, which in turn requires the GROUP COMMIT commit decision set to `raft`. + + +For the details about how Eager conflict resolution works, +see [Eager conflict resolution](../consistency/eager). ### Aborts diff --git a/product_docs/docs/pgd/5/reference/commit-scopes.mdx b/product_docs/docs/pgd/5/reference/commit-scopes.mdx index 4cb9545b41f..dc695c265ff 100644 --- a/product_docs/docs/pgd/5/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/reference/commit-scopes.mdx @@ -74,7 +74,9 @@ A transaction under this commit scope group will be considered committed if a ma Example: `ALL (left_dc)` -A transaction under this commit scope group will be considered committed if all of the nodes in the `left_dc` group confirm they processed the transaction. +A transaction under this commit scope group will be considered committed if all of the nodes in the `left_dc` group confirm they processed the transaction. + +When `ALL` is used with [`GROUP COMMIT`](#group-commit), the [`commit_decision`](#commit_decision-settings) setting must be set to `raft` to avoid reconciliation issues. ### ALL NOT @@ -147,7 +149,7 @@ When set to true, two-phase commit transactions: The value `async` means resolve conflicts asynchronously during replication using the conflict resolution policy. -The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. +The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. The `eager` conflict_resolution setting must only be used with the `ALL` commit scope group, and in turn must be used with a [`commit_decision`](#commit_decision-settings) set to `raft`. See ["Conflict resolution" in Group Commit](../durability/group-commit/#conflict-resolution). @@ -157,12 +159,10 @@ The value `group` means the preceding `commit_scope_group` specification also af The value `partner` means the partner node decides whether transactions can be committed. This value is allowed only on groups with 2 data nodes. -The value `raft` means the COMMIT decision is done using Raft consensus of all the nodes in the cluster, independent of any `commit_scope_group` consensus. This option has low performance and is for backward compatibility only. +The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. This option must be used when the `ALL` commit scope group is being used to ensure no divergence between the nodes over the decision. This option may have low performance. See ["Commit decisions" in Group Commit](../durability/group-commit/#commit-decisions). - - ## CAMO With the client's cooperation, enables protection to prevent multiple insertions of the same transaction in failover scenarios. From 4dd4c02d2e5930f71106ef0815459798dd08c6e3 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 5 Feb 2024 09:34:12 +0000 Subject: [PATCH 06/22] Fixed to say eager+all needs raft (not all only for eager) Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index 996a80ade67..db2f0db9b2a 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -93,8 +93,8 @@ conflict resolution works. Eager means that conflicts are resolved eagerly (as part of agreement on COMMIT), and conflicting transactions get aborted with a serialization error. This approach provides greater isolation than the asynchronous resolution at the -price of performance. Eager resolution should only be used with an `ALL` commit -scope group, which in turn requires the GROUP COMMIT commit decision set to `raft`. +price of performance. When `eager` resolution is used with an `ALL` commit +scope group, the `GROUP COMMIT` commit decision setting must be set to `raft` to avoid reconciliation issues. For the details about how Eager conflict resolution works, From 814ee9311c4a16e72ac38cfc4ea5a66011a48ecf Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 5 Feb 2024 11:14:53 +0000 Subject: [PATCH 07/22] Updated again to unpick unintended restrictions Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 13 ++++++------- product_docs/docs/pgd/5/reference/commit-scopes.mdx | 8 ++++++-- 2 files changed, 12 insertions(+), 9 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index db2f0db9b2a..6102289c224 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -76,9 +76,7 @@ to commit something. This approach requires application changes to use the CAMO transaction protocol to work correctly, as the application is in some way part of the consensus. For more on this approach, see [CAMO](camo). -The `raft` option is for backwards compatibility only. It uses PGD's built-in Raft -consensus for commit decisions. It is slow and only useful with eager conflict -resolution. +The `raft` decision used PGDs built-in raft consensus for commit decisions. It can have low performance and is currently only required when doing eager conflict resolution with an ALL commit scope group. ### Conflict resolution @@ -93,9 +91,9 @@ conflict resolution works. Eager means that conflicts are resolved eagerly (as part of agreement on COMMIT), and conflicting transactions get aborted with a serialization error. This approach provides greater isolation than the asynchronous resolution at the -price of performance. When `eager` resolution is used with an `ALL` commit -scope group, the `GROUP COMMIT` commit decision setting must be set to `raft` to avoid reconciliation issues. - +price of performance. Using eager with an ALL commit scope group requires that +the [commit decision](#commit-decisions) must be set to `raft` to avoid +reconciliation issues. For the details about how Eager conflict resolution works, see [Eager conflict resolution](../consistency/eager). @@ -108,4 +106,5 @@ transaction abort is requested. If the transaction is already decided to be committed at the time the abort request is sent, the transaction does eventually COMMIT even though the client might receive an abort message. -See also [Limitations](limitations). \ No newline at end of file + +See also [Limitations](limitations). \ No newline at end of file diff --git a/product_docs/docs/pgd/5/reference/commit-scopes.mdx b/product_docs/docs/pgd/5/reference/commit-scopes.mdx index dc695c265ff..87da77a1e58 100644 --- a/product_docs/docs/pgd/5/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/reference/commit-scopes.mdx @@ -149,7 +149,9 @@ When set to true, two-phase commit transactions: The value `async` means resolve conflicts asynchronously during replication using the conflict resolution policy. -The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. The `eager` conflict_resolution setting must only be used with the `ALL` commit scope group, and in turn must be used with a [`commit_decision`](#commit_decision-settings) set to `raft`. +The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. + +When this option is used with the `ALL` commit scope group, the [`commit_decision`](#commit_decision-settings) must be set to `raft` to avoid reconcilation issue. See ["Conflict resolution" in Group Commit](../durability/group-commit/#conflict-resolution). @@ -159,7 +161,9 @@ The value `group` means the preceding `commit_scope_group` specification also af The value `partner` means the partner node decides whether transactions can be committed. This value is allowed only on groups with 2 data nodes. -The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. This option must be used when the `ALL` commit scope group is being used to ensure no divergence between the nodes over the decision. This option may have low performance. +The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. + +This option must be used when the `ALL` commit scope group is being used with `eager` conflict resolution to ensure no divergence between the nodes over the decision. This option may have low performance. See ["Commit decisions" in Group Commit](../durability/group-commit/#commit-decisions). From 1c2194678124ac9d0eeec3fb77576170e1162a3b Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 5 Feb 2024 12:56:20 +0000 Subject: [PATCH 08/22] typo fix Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index 6102289c224..27d66758410 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -76,7 +76,7 @@ to commit something. This approach requires application changes to use the CAMO transaction protocol to work correctly, as the application is in some way part of the consensus. For more on this approach, see [CAMO](camo). -The `raft` decision used PGDs built-in raft consensus for commit decisions. It can have low performance and is currently only required when doing eager conflict resolution with an ALL commit scope group. +The `raft` decision uses PGDs built-in raft consensus for commit decisions. It can have low performance and is currently only required when doing eager conflict resolution with an ALL commit scope group. ### Conflict resolution From 08834562f97999e2397352fbfad79ddc8b0e222a Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 5 Feb 2024 13:29:15 +0000 Subject: [PATCH 09/22] fixing again Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/durability/group-commit.mdx | 10 ++++++---- product_docs/docs/pgd/5/reference/commit-scopes.mdx | 2 +- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/group-commit.mdx b/product_docs/docs/pgd/5/durability/group-commit.mdx index 27d66758410..5b5705ea0df 100644 --- a/product_docs/docs/pgd/5/durability/group-commit.mdx +++ b/product_docs/docs/pgd/5/durability/group-commit.mdx @@ -76,7 +76,7 @@ to commit something. This approach requires application changes to use the CAMO transaction protocol to work correctly, as the application is in some way part of the consensus. For more on this approach, see [CAMO](camo). -The `raft` decision uses PGDs built-in raft consensus for commit decisions. It can have low performance and is currently only required when doing eager conflict resolution with an ALL commit scope group. +The `raft` decision uses PGDs built-in raft consensus for commit decisions. It can have low performance and is currently only required when using GROUP COMMIT with an ALL commit scope group. ### Conflict resolution @@ -91,9 +91,11 @@ conflict resolution works. Eager means that conflicts are resolved eagerly (as part of agreement on COMMIT), and conflicting transactions get aborted with a serialization error. This approach provides greater isolation than the asynchronous resolution at the -price of performance. Using eager with an ALL commit scope group requires that -the [commit decision](#commit-decisions) must be set to `raft` to avoid -reconciliation issues. +price of performance. + +Using an ALL commit scope group requires that the [commit +decision](#commit-decisions) must be set to `raft` to avoid reconciliation +issues. For the details about how Eager conflict resolution works, see [Eager conflict resolution](../consistency/eager). diff --git a/product_docs/docs/pgd/5/reference/commit-scopes.mdx b/product_docs/docs/pgd/5/reference/commit-scopes.mdx index 87da77a1e58..dd0cdd46517 100644 --- a/product_docs/docs/pgd/5/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/reference/commit-scopes.mdx @@ -163,7 +163,7 @@ The value `partner` means the partner node decides whether transactions can be c The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. -This option must be used when the `ALL` commit scope group is being used with `eager` conflict resolution to ensure no divergence between the nodes over the decision. This option may have low performance. +This option must be used when the `ALL` commit scope group is being used to ensure no divergence between the nodes over the decision. This option may have low performance. See ["Commit decisions" in Group Commit](../durability/group-commit/#commit-decisions). From 02252eec0ff734865f9856a1a8c320912119c524 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 5 Feb 2024 14:57:43 +0000 Subject: [PATCH 10/22] More changes Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/consistency/eager.mdx | 2 ++ product_docs/docs/pgd/5/reference/commit-scopes.mdx | 8 ++++++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/consistency/eager.mdx b/product_docs/docs/pgd/5/consistency/eager.mdx index 617076f6973..40dcc2b97e5 100644 --- a/product_docs/docs/pgd/5/consistency/eager.mdx +++ b/product_docs/docs/pgd/5/consistency/eager.mdx @@ -40,6 +40,8 @@ SELECT bdr.add_commit_scope( !!! note Upgrading? The old `global` commit scope doesn't exist anymore. The above command creates a scope that's the same as the old `global` scope with `bdr.global_commit_timeout` set to `60s`. +The commit scope group for the eager conflict resolution rule can only be `ALL` or `MAJORITY`. Where `ALL` is used, the `commit_decision` setting must also be set to `raft`. + ## Error handling Given that PGD manages the transaction, the client needs to check only the result of the `COMMIT`. This is advisable in any case, including single-node Postgres. diff --git a/product_docs/docs/pgd/5/reference/commit-scopes.mdx b/product_docs/docs/pgd/5/reference/commit-scopes.mdx index dd0cdd46517..36fefb88fb8 100644 --- a/product_docs/docs/pgd/5/reference/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/reference/commit-scopes.mdx @@ -151,7 +151,11 @@ The value `async` means resolve conflicts asynchronously during replication usin The value `eager` means that conflicts are resolved eagerly during COMMIT by aborting one of the conflicting transactions. -When this option is used with the `ALL` commit scope group, the [`commit_decision`](#commit_decision-settings) must be set to `raft` to avoid reconcilation issue. +Eager is only available with `MAJORITY` or `ALL` commit scope groups. + +When used with the `ALL` commit scope group, the [`commit_decision`](#commit_decision-settings) must be set to `raft` to avoid reconcilation issue. + + See ["Conflict resolution" in Group Commit](../durability/group-commit/#conflict-resolution). @@ -161,7 +165,7 @@ The value `group` means the preceding `commit_scope_group` specification also af The value `partner` means the partner node decides whether transactions can be committed. This value is allowed only on groups with 2 data nodes. -The value `raft` means the COMMIT decision is noted using Raft consensus of all nodes, after the nodes in the `commit_scope_group` have confirmed. This ensures that all nodes have a consensus on the decision. +The value `raft` means the decision makes use of PGD's built-in Raft consensus. Once all the nodes in the selected commit scope group have confirmed the transaction, to ensure that all the nodes in the PGD cluster have noted the transaction, it is noted with the all-node Raft. This option must be used when the `ALL` commit scope group is being used to ensure no divergence between the nodes over the decision. This option may have low performance. From 73315b1979f0311fb2ceb76d9515402b5b5adda0 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 7 Feb 2024 15:16:11 +0000 Subject: [PATCH 11/22] Added subscription and writer Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5/terminology.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/product_docs/docs/pgd/5/terminology.mdx b/product_docs/docs/pgd/5/terminology.mdx index 7718d7191a5..8e759c54522 100644 --- a/product_docs/docs/pgd/5/terminology.mdx +++ b/product_docs/docs/pgd/5/terminology.mdx @@ -98,6 +98,10 @@ A consensus algorithm that uses votes from a quorum of machines in a distributed The ability of a system to handle increasing read workloads. For example, PGD can introduce one or more read replica nodes to a cluster and have the application direct writes to the primary node and reads to the replica nodes. As the read workload grows, you can increase the number of read replica nodes to maintain performance. +#### Subscription + +PGD nodes will publish changes being made to data to nodes that are interested. Other PGD nodes will ask to subscribe to those changes. This creates a subscription and is the mechanism by which each node is updated. PGD nodes bidirectionally subscribe to other PGD node's changes. + #### Switchover A planned change in connection between the application or proxies and the active database node in a cluster, typically done for maintenance. @@ -133,3 +137,8 @@ Witness nodes primarily serve to help the cluster establish a consensus. An odd #### Write leader In an Always-On architecture, a node is selected as the correct connection endpoint for applications. This node is called the write leader. Once selected, proxy nodes route queries and updates to it. With only one node receiving writes, unintended multi-node writes can be avoided. The write leader is selected by consensus of a quorum of data nodes. If the write leader becomes unavailable, the data nodes select another node to become write leader. Nodes that aren't the write leader are referred to as *shadow nodes*. + +#### Writer + + When a [subscription](#subscription) delivers data changes to a PGD node, the database server tasks a worker process called a writer with getting those changes recorded. + From f07519caf35cb09aba4092faa4f6d7e50cd6018f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Wed, 7 Feb 2024 15:34:31 +0000 Subject: [PATCH 12/22] Update product_docs/docs/pgd/5/terminology.mdx Co-authored-by: Nick Babadzhanian <33933459+pgnickb@users.noreply.github.com> --- product_docs/docs/pgd/5/terminology.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/terminology.mdx b/product_docs/docs/pgd/5/terminology.mdx index 8e759c54522..096b24edcab 100644 --- a/product_docs/docs/pgd/5/terminology.mdx +++ b/product_docs/docs/pgd/5/terminology.mdx @@ -140,5 +140,5 @@ In an Always-On architecture, a node is selected as the correct connection endpo #### Writer - When a [subscription](#subscription) delivers data changes to a PGD node, the database server tasks a worker process called a writer with getting those changes recorded. + When a [subscription](#subscription) delivers data changes to a PGD node, the database server tasks a worker process called a writer with getting those changes applied. From a4f928187b819db0765bb6f49f1d3f9cf654615d Mon Sep 17 00:00:00 2001 From: jingjingliu20 <86595232+jingjingliu20@users.noreply.github.com> Date: Mon, 29 Jan 2024 18:49:52 +0800 Subject: [PATCH 13/22] Update index.mdx Remove the southeastasia notes, the Faraway is already supported there. --- .../biganimal/release/overview/03a_region_support/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx index f5d060891d7..d42699ae484 100644 --- a/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx +++ b/product_docs/docs/biganimal/release/overview/03a_region_support/index.mdx @@ -54,7 +54,7 @@ When using Azure, you can create clusters in the following regions. | Australia East | australiaeast | | | Central India | centralindia | | | Japan East | japaneast | | -| Southeast Asia | southeastasia | Does not support the creation of faraway replicas | +| Southeast Asia | southeastasia | | ### AWS regions From 78ce06078b48b4d769684eb61284e7e84b658ab0 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Wed, 7 Feb 2024 17:25:35 +0000 Subject: [PATCH 14/22] Correct release year to 2024 --- product_docs/docs/tpa/23/rel_notes/index.mdx | 2 +- product_docs/docs/tpa/23/rel_notes/tpa_23.28_rel_notes.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx index 708ab82ead9..963d8c8cf2a 100644 --- a/product_docs/docs/tpa/23/rel_notes/index.mdx +++ b/product_docs/docs/tpa/23/rel_notes/index.mdx @@ -26,7 +26,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru | Version | Release date | | ---------------------------- | ------------ | -| [23.28](tpa_23.28_rel_notes) | 23 Jan 2023 | +| [23.28](tpa_23.28_rel_notes) | 23 Jan 2024 | | [23.27](tpa_23.27_rel_notes) | 19 Dec 2023 | | [23.26](tpa_23.26_rel_notes) | 30 Nov 2023 | | [23.25](tpa_23.25_rel_notes) | 14 Nov 2023 | diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.28_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.28_rel_notes.mdx index 9e321d0b3de..bcf5c294db2 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.28_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.28_rel_notes.mdx @@ -3,7 +3,7 @@ title: Trusted Postgres Architect 23.28 release notes navTitle: "Version 23.28" --- -Released: 23 Jan 2023 +Released: 23 Jan 2024 New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.28 include the following: From 550e62dafc0f0d4b88d3ca2b1d251ff91e7ad1cb Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 9 Feb 2024 09:25:51 +0000 Subject: [PATCH 15/22] Removed the verification and policy sections from security Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/3.7/bdr/security.mdx | 64 ---------------------- product_docs/docs/pgd/4/bdr/security.mdx | 64 ---------------------- 2 files changed, 128 deletions(-) diff --git a/product_docs/docs/pgd/3.7/bdr/security.mdx b/product_docs/docs/pgd/3.7/bdr/security.mdx index a2dcc1322a4..68e0c48f7eb 100644 --- a/product_docs/docs/pgd/3.7/bdr/security.mdx +++ b/product_docs/docs/pgd/3.7/bdr/security.mdx @@ -325,67 +325,3 @@ to read the conflict history. If it is useful to have a user that can see conflicts for *all* tables, you may optionally grant the role *bdr_read_all_conflicts* to that user. -## Verification - -BDR has been verified using the following tools and approaches. - -### Coverity - -Coverity Scan has been used to verify the BDR stack providing coverage -against vulnerabilities using the following rules and coding standards: - -- MISRA C -- ISO 26262 -- ISO/IEC TS 17961 -- OWASP Top 10 -- CERT C -- CWE Top 25 -- AUTOSAR - -### CIS Benchmark - -CIS PostgreSQL Benchmark v1, 19 Dec 2019 has been used to verify the BDR stack. -Using the `cis_policy.yml` configuration available as an option with TPAexec -gives the following results for the Scored tests: - -| | Result | Description | -| ------ | ---------- | ----------------------------------------------------------------- | -| 1.4 | PASS | Ensure systemd Service Files Are Enabled | -| 1.5 | PASS | Ensure Data Cluster Initialized Successfully | -| 2.1 | PASS | Ensure the file permissions mask is correct | -| 2.2 | PASS | Ensure the PostgreSQL pg_wheel group membership is correct | -| 3.1.2 | PASS | Ensure the log destinations are set correctly | -| 3.1.3 | PASS | Ensure the logging collector is enabled | -| 3.1.4 | PASS | Ensure the log file destination directory is set correctly | -| 3.1.5 | PASS | Ensure the filename pattern for log files is set correctly | -| 3.1.6 | PASS | Ensure the log file permissions are set correctly | -| 3.1.7 | PASS | Ensure 'log_truncate_on_rotation' is enabled | -| 3.1.8 | PASS | Ensure the maximum log file lifetime is set correctly | -| 3.1.9 | PASS | Ensure the maximum log file size is set correctly | -| 3.1.10 | PASS | Ensure the correct syslog facility is selected | -| 3.1.11 | PASS | Ensure the program name for PostgreSQL syslog messages is correct | -| 3.1.14 | PASS | Ensure 'debug_print_parse' is disabled | -| 3.1.15 | PASS | Ensure 'debug_print_rewritten' is disabled | -| 3.1.16 | PASS | Ensure 'debug_print_plan' is disabled | -| 3.1.17 | PASS | Ensure 'debug_pretty_print' is enabled | -| 3.1.18 | PASS | Ensure 'log_connections' is enabled | -| 3.1.19 | PASS | Ensure 'log_disconnections' is enabled | -| 3.1.21 | PASS | Ensure 'log_hostname' is set correctly | -| 3.1.23 | PASS | Ensure 'log_statement' is set correctly | -| 3.1.24 | PASS | Ensure 'log_timezone' is set correctly | -| 3.2 | PASS | Ensure the PostgreSQL Audit Extension (pgAudit) is enabled | -| 4.1 | PASS | Ensure sudo is configured correctly | -| 4.2 | PASS | Ensure excessive administrative privileges are revoked | -| 4.3 | PASS | Ensure excessive function privileges are revoked | -| 4.4 | PASS | Tested Ensure excessive DML privileges are revoked | -| 5.2 | Not Tested | Ensure login via 'host' TCP/IP Socket is configured correctly | -| 6.2 | PASS | Ensure 'backend' runtime parameters are configured correctly | -| 6.7 | Not Tested | Ensure FIPS 140-2 OpenSSL Cryptography Is Used | -| 6.8 | PASS | Ensure SSL is enabled and configured correctly | -| 7.3 | PASS | Ensure WAL archiving is configured and functional | - -Note that test 5.2 can PASS if audited manually, but does not have an -automatable test. - -Test 6.7 succeeds on default deployments using CentOS, but it -requires extra packages on Debian variants. diff --git a/product_docs/docs/pgd/4/bdr/security.mdx b/product_docs/docs/pgd/4/bdr/security.mdx index ed348f4c31d..099d39e8c90 100644 --- a/product_docs/docs/pgd/4/bdr/security.mdx +++ b/product_docs/docs/pgd/4/bdr/security.mdx @@ -318,67 +318,3 @@ to read the conflict history. If it's useful to have a user that can see conflicts for all tables, you can optionally grant the role bdr_read_all_conflicts to that user. -## Verification - -BDR was verified using the following tools and approaches. - -### Coverity - -Coverity Scan was used to verify the BDR stack providing coverage -against vulnerabilities using the following rules and coding standards: - -- MISRA C -- ISO 26262 -- ISO/IEC TS 17961 -- OWASP Top 10 -- CERT C -- CWE Top 25 -- AUTOSAR - -### CIS Benchmark - -CIS PostgreSQL Benchmark v1, 19 Dec 2019 was used to verify the BDR stack. -Using the `cis_policy.yml` configuration available as an option with TPAexec -gives the following results for the Scored tests: - -| | Result | Description | -| ------ | ---------- | ----------------------------------------------------------------- | -| 1.4 | PASS | Ensure systemd Service Files Are Enabled | -| 1.5 | PASS | Ensure Data Cluster Initialized Successfully | -| 2.1 | PASS | Ensure the file permissions mask is correct | -| 2.2 | PASS | Ensure the PostgreSQL pg_wheel group membership is correct | -| 3.1.2 | PASS | Ensure the log destinations are set correctly | -| 3.1.3 | PASS | Ensure the logging collector is enabled | -| 3.1.4 | PASS | Ensure the log file destination directory is set correctly | -| 3.1.5 | PASS | Ensure the filename pattern for log files is set correctly | -| 3.1.6 | PASS | Ensure the log file permissions are set correctly | -| 3.1.7 | PASS | Ensure 'log_truncate_on_rotation' is enabled | -| 3.1.8 | PASS | Ensure the maximum log file lifetime is set correctly | -| 3.1.9 | PASS | Ensure the maximum log file size is set correctly | -| 3.1.10 | PASS | Ensure the correct syslog facility is selected | -| 3.1.11 | PASS | Ensure the program name for PostgreSQL syslog messages is correct | -| 3.1.14 | PASS | Ensure 'debug_print_parse' is disabled | -| 3.1.15 | PASS | Ensure 'debug_print_rewritten' is disabled | -| 3.1.16 | PASS | Ensure 'debug_print_plan' is disabled | -| 3.1.17 | PASS | Ensure 'debug_pretty_print' is enabled | -| 3.1.18 | PASS | Ensure 'log_connections' is enabled | -| 3.1.19 | PASS | Ensure 'log_disconnections' is enabled | -| 3.1.21 | PASS | Ensure 'log_hostname' is set correctly | -| 3.1.23 | PASS | Ensure 'log_statement' is set correctly | -| 3.1.24 | PASS | Ensure 'log_timezone' is set correctly | -| 3.2 | PASS | Ensure the PostgreSQL Audit Extension (pgAudit) is enabled | -| 4.1 | PASS | Ensure sudo is configured correctly | -| 4.2 | PASS | Ensure excessive administrative privileges are revoked | -| 4.3 | PASS | Ensure excessive function privileges are revoked | -| 4.4 | PASS | Tested Ensure excessive DML privileges are revoked | -| 5.2 | Not Tested | Ensure login via 'host' TCP/IP Socket is configured correctly | -| 6.2 | PASS | Ensure 'backend' runtime parameters are configured correctly | -| 6.7 | Not Tested | Ensure FIPS 140-2 OpenSSL Cryptography Is Used | -| 6.8 | PASS | Ensure SSL is enabled and configured correctly | -| 7.3 | PASS | Ensure WAL archiving is configured and functional | - -Test 5.2 can PASS if audited manually, but it doesn't have an -automated test. - -Test 6.7 succeeds on default deployments using CentOS, but it -requires extra packages on Debian variants. From 43c706c3cdf0657298d25e7a163567ac32a402b8 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Fri, 9 Feb 2024 18:03:47 +0000 Subject: [PATCH 16/22] Add hidePDF: true to hide the PDF panel on any page. Signed-off-by: Dj Walker-Morgan --- gatsby-node.js | 3 +++ product_docs/docs/bart/2.6/index.mdx | 1 + src/components/icon/iconNames.js | 2 -- src/components/left-nav.js | 3 ++- src/components/pdf-download.js | 6 +++++- src/templates/doc.js | 3 ++- 6 files changed, 13 insertions(+), 5 deletions(-) diff --git a/gatsby-node.js b/gatsby-node.js index bf6df39d0aa..699c2431bfa 100644 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -172,6 +172,7 @@ exports.createPages = async ({ actions, graphql, reporter }) => { codelanguages } hideVersion + hidePDF displayBanner directoryDefaults { description @@ -514,6 +515,7 @@ exports.createSchemaCustomization = ({ actions }) => { hideToC: Boolean deepToC: Boolean hideVersion: Boolean + hidePDF: Boolean hideKBLink: Boolean displayBanner: String directoryDefaults: DirectoryDefaults @@ -541,6 +543,7 @@ exports.createSchemaCustomization = ({ actions }) => { editTarget: EditTargets showInteractiveBadge: Boolean hideVersion: Boolean + hidePDF: Boolean hideKBLink: Boolean displayBanner: String } diff --git a/product_docs/docs/bart/2.6/index.mdx b/product_docs/docs/bart/2.6/index.mdx index 0a231decd98..ecdea5c7285 100644 --- a/product_docs/docs/bart/2.6/index.mdx +++ b/product_docs/docs/bart/2.6/index.mdx @@ -2,6 +2,7 @@ title: Backup and Recovery Tool directoryDefaults: description: "EDB Backup and Recovery Tool Version 2.6.1 - End Of Life" +hidePDF: true --- Backup and Recovery Tool reached its end of life in 2023. diff --git a/src/components/icon/iconNames.js b/src/components/icon/iconNames.js index 6c216ce9dcf..7ea90db057f 100644 --- a/src/components/icon/iconNames.js +++ b/src/components/icon/iconNames.js @@ -101,7 +101,6 @@ const iconNames = { INSTANCES: "Instances", INTEGRATION: "Integration", KNIGHT: "Knight", - KUBERNETES: "Kubernetes", LAPTOP_CONFIG: "LaptopConfig", LEADER: "Leader", LEARNING: "Learning", @@ -129,7 +128,6 @@ const iconNames = { PLANNER: "Planner", PLAY_CIRCLE: "PlayCircle", PLUS: "Plus", - POSTGRESQL: "Postgresql", PREFERENCES: "Preferences", PRESENTATION: "Presentation", PROCESS: "Process", diff --git a/src/components/left-nav.js b/src/components/left-nav.js index 0b30f1529af..194d8dfd7dc 100644 --- a/src/components/left-nav.js +++ b/src/components/left-nav.js @@ -70,6 +70,7 @@ const LeftNav = ({ iconName, hideEmptySections = false, hideVersion = false, + hidePDF = false, }) => { return (
    @@ -93,7 +94,7 @@ const LeftNav = ({ /> ))}
  • - +
); diff --git a/src/components/pdf-download.js b/src/components/pdf-download.js index da7306a3d3e..b02728f95ef 100644 --- a/src/components/pdf-download.js +++ b/src/components/pdf-download.js @@ -3,7 +3,7 @@ import { useStaticQuery, graphql } from "gatsby"; import Icon, { iconNames } from "./icon"; import usePathPrefix from "../hooks/use-path-prefix"; -const PdfDownload = ({ pagePath }) => { +const PdfDownload = ({ pagePath, hidePDF }) => { const data = useStaticQuery(graphql` { allPublicFile(filter: { ext: { eq: ".pdf" } }) { @@ -27,6 +27,10 @@ const PdfDownload = ({ pagePath }) => { const pathPrefix = usePathPrefix(); + if (hidePDF) { + return null; + } + if (file) { return (
diff --git a/src/templates/doc.js b/src/templates/doc.js index cdabef0d16b..6787c349108 100644 --- a/src/templates/doc.js +++ b/src/templates/doc.js @@ -215,8 +215,8 @@ const DocTemplate = ({ data, pageContext }) => { editTarget, originalFilePath, deepToC, + hidePDF, } = frontmatter; - // don't encourage folks to edit on main - set the edit links to develop in production builds const branch = gitData.branch === "main" ? "develop" : gitData.branch; const fileUrlSegment = fileAbsolutePath.split("/product_docs/docs").slice(1); @@ -271,6 +271,7 @@ const DocTemplate = ({ data, pageContext }) => { versionArray={versionArray} iconName={iconName} hideVersion={frontmatter.hideVersion} + hidePDF={hidePDF} /> From d04c9218aa9623aa87d854a30e4bb39d3815dd5b Mon Sep 17 00:00:00 2001 From: Phil Eaton Date: Mon, 12 Feb 2024 14:32:49 -0500 Subject: [PATCH 17/22] Consistent use of tick formatting of variable names And also consistent punctuation before a code sample. --- product_docs/docs/pgd/5/durability/commit-scopes.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/pgd/5/durability/commit-scopes.mdx b/product_docs/docs/pgd/5/durability/commit-scopes.mdx index bbd3f34425d..3f517eba6eb 100644 --- a/product_docs/docs/pgd/5/durability/commit-scopes.mdx +++ b/product_docs/docs/pgd/5/durability/commit-scopes.mdx @@ -14,13 +14,13 @@ Every commit scope has a name (a `commit_scope_name`). Each commit scope has one or more rules. -Each rule within the commit scope has an origin_node_group which together uniquely identify the commit scope rule. +Each rule within the commit scope has an `origin_node_group` which together uniquely identify the commit scope rule. -The origin_node_group is a PGD group and it defines the nodes which will apply this rule when they are the originators of a transaction. +The `origin_node_group` is a PGD group and it defines the nodes which will apply this rule when they are the originators of a transaction. Finally there is the rule which defines what kind of commit scope or combination of commit scope kinds should be applied to those transactions. -So if a commit scope has a rule that reads +So if a commit scope has a rule that reads: origin_node_group := 'example_bdr_group', rule := 'ANY 2 (example_bdr_group) GROUP COMMIT', From dc581616031f46a506cc56006b104aa13a2a2712 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 8 Feb 2024 21:03:15 +0000 Subject: [PATCH 18/22] Perform API HTML+link corrections on import; Use a worktree for the script to avoid messing up the source repo (can now re-run local import without side-effects) --- ...rip-html-comments.mjs => cleanup-html.mjs} | 7 +++-- .../processors/cnp/update-links.mjs | 3 ++ scripts/source/process-cnp-docs.sh | 28 +++++++++++++------ 3 files changed, 28 insertions(+), 10 deletions(-) rename scripts/fileProcessor/processors/cnp/{strip-html-comments.mjs => cleanup-html.mjs} (82%) diff --git a/scripts/fileProcessor/processors/cnp/strip-html-comments.mjs b/scripts/fileProcessor/processors/cnp/cleanup-html.mjs similarity index 82% rename from scripts/fileProcessor/processors/cnp/strip-html-comments.mjs rename to scripts/fileProcessor/processors/cnp/cleanup-html.mjs index 41f0ddd6113..e1a8cc342fb 100644 --- a/scripts/fileProcessor/processors/cnp/strip-html-comments.mjs +++ b/scripts/fileProcessor/processors/cnp/cleanup-html.mjs @@ -1,5 +1,5 @@ -// HTML comments () are not valid in MDX -// strip them out completely +// HTML comments () are not valid in MDX - strip them out completely +// ensure tags are lowercase import toVFile from "to-vfile"; import remarkParse from "remark-parse"; @@ -45,6 +45,9 @@ function stripComments() { // strip (potentially NON-EMPTY) HTML comments - these are not valid in JSX node.value = node.value.replace(/(?=/g, ""); + + // lower-case HTML tags + node.value = node.value.replace(/<(\/*)(\w+)([^>]*)>/g, (match, close, tag, rest) => `<${close}${tag.toLowerCase()}${rest}>`) }); }; } diff --git a/scripts/fileProcessor/processors/cnp/update-links.mjs b/scripts/fileProcessor/processors/cnp/update-links.mjs index 36ef8e0336c..a78a15c5c6f 100644 --- a/scripts/fileProcessor/processors/cnp/update-links.mjs +++ b/scripts/fileProcessor/processors/cnp/update-links.mjs @@ -44,6 +44,7 @@ function linkRewriter() { // - update links to release_notes to rel_notes // - update links to appendixes/* to /* // - update links *from* appendixes/* to /* + // - update links to cloudnative-pg.v1.md to pg4k.v1.md visit(tree, ["link", "yaml"], (node) => { if (node.type === "yaml") { @@ -62,6 +63,8 @@ function linkRewriter() { node.url = "rel_notes"; else if (node.url === "release_notes.md") node.url = "rel_notes"; + else if (node.url.includes("cloudnative-pg.v1.md")) + node.url = node.url.replace("cloudnative-pg.v1.md", "pg4k.v1.md"); }); }; } diff --git a/scripts/source/process-cnp-docs.sh b/scripts/source/process-cnp-docs.sh index 02403e0407b..7e8419b1d4a 100755 --- a/scripts/source/process-cnp-docs.sh +++ b/scripts/source/process-cnp-docs.sh @@ -6,6 +6,8 @@ then exit 1 fi +CWD=`pwd` + # convert inputs to actual directory names, in case a relative path is passed in. SOURCE_CHECKOUT=`cd $1 && pwd` DESTINATION_CHECKOUT=`cd $2 && pwd` @@ -13,15 +15,20 @@ DESTINATION_CHECKOUT=`cd $2 && pwd` cd $DESTINATION_CHECKOUT/scripts/fileProcessor npm ci +cd $SOURCE_CHECKOUT + +# create a temporary worktree to avoid messing up source repo (for local work; CI doesn't care) +git worktree add --detach ./docs-import + cd $DESTINATION_CHECKOUT/product_docs/docs/postgres_for_kubernetes/1/ node $DESTINATION_CHECKOUT/scripts/source/files-to-ignore.mjs \ "$DESTINATION_CHECKOUT/product_docs/docs/postgres_for_kubernetes/1/" \ - > $SOURCE_CHECKOUT/files-to-ignore.txt + > $SOURCE_CHECKOUT/docs-import/files-to-ignore.txt -cd $SOURCE_CHECKOUT/docs +cd $SOURCE_CHECKOUT/docs-import/docs # grab key bit of source for use in docs -cp $SOURCE_CHECKOUT/config/manager/default-monitoring.yaml $SOURCE_CHECKOUT/docs/src/ +cp $SOURCE_CHECKOUT/docs-import/config/manager/default-monitoring.yaml $SOURCE_CHECKOUT/docs-import/docs/src/ node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -f "src/**/quickstart.md" \ @@ -35,13 +42,18 @@ node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -p "cnp/update-links" \ -p "cnp/update-yaml-links" \ -p "cnp/rewrite-mdextra-anchors" \ - -p "cnp/strip-html-comments" \ + -p "cnp/cleanup-html" \ -p "cnp/rename-to-mdx" node $DESTINATION_CHECKOUT/scripts/source/merge-indexes.mjs \ - "$SOURCE_CHECKOUT/docs/src/index.mdx" \ + "$SOURCE_CHECKOUT/docs-import/docs/src/index.mdx" \ "$DESTINATION_CHECKOUT/product_docs/docs/postgres_for_kubernetes/1/index.mdx" \ - "$SOURCE_CHECKOUT/docs/src/index.mdx" \ - >> $SOURCE_CHECKOUT/files-to-ignore.txt + "$SOURCE_CHECKOUT/docs-import/docs/src/index.mdx" \ + >> $SOURCE_CHECKOUT/docs-import/files-to-ignore.txt + +rsync -av --delete --exclude-from=$SOURCE_CHECKOUT/docs-import/files-to-ignore.txt src/ $DESTINATION_CHECKOUT/product_docs/docs/postgres_for_kubernetes/1/ -rsync -av --delete --exclude-from=$SOURCE_CHECKOUT/files-to-ignore.txt src/ $DESTINATION_CHECKOUT/product_docs/docs/postgres_for_kubernetes/1/ +# cleanup: remove worktree +cd $SOURCE_CHECKOUT +git worktree remove --force ./docs-import +cd $CWD From 0c039d74f6f6279b54d3f55899acd579195baa1a Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Mon, 12 Feb 2024 22:46:24 +0000 Subject: [PATCH 19/22] Same enhancements for the PG4K-PGD script --- scripts/source/process-pgd4k-docs.sh | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/scripts/source/process-pgd4k-docs.sh b/scripts/source/process-pgd4k-docs.sh index 052c5db1d1a..11e65fd1cce 100755 --- a/scripts/source/process-pgd4k-docs.sh +++ b/scripts/source/process-pgd4k-docs.sh @@ -13,24 +13,35 @@ DESTINATION_CHECKOUT=`cd $2 && pwd` cd $DESTINATION_CHECKOUT/scripts/fileProcessor npm install --production +cd $SOURCE_CHECKOUT + +# create a temporary worktree to avoid messing up source repo (for local work; CI doesn't care) +git worktree add --detach ./docs-import + cd $DESTINATION_CHECKOUT/product_docs/docs/postgres_distributed_for_kubernetes/1/ node $DESTINATION_CHECKOUT/scripts/source/files-to-ignore.mjs \ "$DESTINATION_CHECKOUT/product_docs/docs/postgres_distributed_for_kubernetes/1/" \ - > $SOURCE_CHECKOUT/files-to-ignore.txt + > $SOURCE_CHECKOUT/docs-import/files-to-ignore.txt -cd $SOURCE_CHECKOUT/docs +cd $SOURCE_CHECKOUT/docs-import/docs node $DESTINATION_CHECKOUT/scripts/fileProcessor/main.mjs \ -f "src/**/*.md" \ -p "cnp/replace-github-urls" \ -p "cnp/update-yaml-links" \ -p "cnp/add-frontmatters" \ + -p "cnp/cleanup-html" \ -p "cnp/rename-to-mdx" node $DESTINATION_CHECKOUT/scripts/source/merge-indexes.mjs \ - "$SOURCE_CHECKOUT/docs/src/index.mdx" \ + "$SOURCE_CHECKOUT/docs-import/docs/src/index.mdx" \ "$DESTINATION_CHECKOUT/product_docs/docs/postgres_distributed_for_kubernetes/1/index.mdx" \ - "$SOURCE_CHECKOUT/docs/src/index.mdx" \ - >> $SOURCE_CHECKOUT/files-to-ignore.txt + "$SOURCE_CHECKOUT/docs-import/docs/src/index.mdx" \ + >> $SOURCE_CHECKOUT/docs-import/files-to-ignore.txt + +rsync -av --delete --exclude-from=$SOURCE_CHECKOUT/docs-import/files-to-ignore.txt src/ $DESTINATION_CHECKOUT/product_docs/docs/postgres_distributed_for_kubernetes/1/ -rsync -av --delete --exclude-from=$SOURCE_CHECKOUT/files-to-ignore.txt src/ $DESTINATION_CHECKOUT/product_docs/docs/postgres_distributed_for_kubernetes/1/ +# cleanup: remove worktree +cd $SOURCE_CHECKOUT +git worktree remove --force ./docs-import +cd $CWD From 12093f814b26cb2cbfff9b62d2882869f530ca83 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Sat, 10 Feb 2024 14:16:05 +0000 Subject: [PATCH 20/22] Minor release updates, all upstream merges on epas and pge Signed-off-by: Dj Walker-Morgan --- .../12/epas_rel_notes/epas12_18_23_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/12/epas_rel_notes/index.mdx | 2 ++ .../13/epas_rel_notes/epas13_14_20_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/13/epas_rel_notes/index.mdx | 2 ++ .../14/epas_rel_notes/epas14_11_0_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/14/epas_rel_notes/index.mdx | 2 ++ .../15/epas_rel_notes/epas15_6_0_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/15/epas_rel_notes/index.mdx | 2 ++ .../16/epas_rel_notes/epas16_2_0_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/16/epas_rel_notes/index.mdx | 2 ++ product_docs/docs/pge/15/release_notes/index.mdx | 2 ++ .../docs/pge/15/release_notes/rel_notes15.6.mdx | 16 ++++++++++++++++ product_docs/docs/pge/16/release_notes/index.mdx | 2 ++ .../docs/pge/16/release_notes/rel_notes16.2.mdx | 12 ++++++++++++ 14 files changed, 102 insertions(+) create mode 100644 product_docs/docs/epas/12/epas_rel_notes/epas12_18_23_rel_notes.mdx create mode 100644 product_docs/docs/epas/13/epas_rel_notes/epas13_14_20_rel_notes.mdx create mode 100644 product_docs/docs/epas/14/epas_rel_notes/epas14_11_0_rel_notes.mdx create mode 100644 product_docs/docs/epas/15/epas_rel_notes/epas15_6_0_rel_notes.mdx create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx create mode 100644 product_docs/docs/pge/15/release_notes/rel_notes15.6.mdx create mode 100644 product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_18_23_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_18_23_rel_notes.mdx new file mode 100644 index 00000000000..2f5ed7dabb6 --- /dev/null +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_18_23_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 12.18.23 release notes +navTitle: "Version 12.18.23" +--- + +Released: 8 Feb 2024 + +EDB Postgres Advanced Server 12.18.23 includes the following enhancements and bug fixes: + +| Type | Description | Category | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Upstream merge | Merged with community PostgreSQL 12.18. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 12.18 Release Notes](https://www.postgresql.org/docs/release/12.18/) for more information. \ No newline at end of file diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 3ed0dce58b6..9aa310ff3d2 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas12_18_0_rel_notes - epas12_17_22_rel_notes - epas12_16_21_rel_notes - epas12_16_20_rel_notes @@ -29,6 +30,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ----------------------------------------- | ------------ | -------------------------------------------------------------- | +| [12.18.23](epas12_18_23_rel_notes.mdx) | 08 Feb 2023 | [12.18](https://www.postgresql.org/docs/12/release-12-18.html) | | [12.17.22](epas12_17_22_rel_notes.mdx) | 09 Nov 2023 | [12.17](https://www.postgresql.org/docs/12/release-12-17.html) | | [12.16.21](epas12_16_21_rel_notes.mdx) | 25 Sep 2023 | | | [12.16.20](epas12_16_20_rel_notes.mdx) | 21 Aug 2023 | [12.16](https://www.postgresql.org/docs/12/release-12-16.html) | diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_14_20_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_14_20_rel_notes.mdx new file mode 100644 index 00000000000..00fc156678b --- /dev/null +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_14_20_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 13.14.20 release notes +navTitle: "Version 13.14.20" +--- + +Released: 8 Feb 2024 + +EDB Postgres Advanced Server 13.14.20 includes the following enhancements and bug fixes: + +| Type | Description | Category | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Upstream merge | Merged with community PostgreSQL 13.14. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 13.14 Release Notes](https://www.postgresql.org/docs/release/13.14/) for more information. \ No newline at end of file diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index c14b2da3f55..961136f605e 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas13_14_0_rel_notes - epas13_13_19_rel_notes - epas13_12_18_rel_notes - epas13_12_17_rel_notes @@ -22,6 +23,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ----------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------- | +| [13.14.20](epas13_14_20_rel_notes) | 08 Feb 2024 | [13.14](https://www.postgresql.org/docs/release/13.14/) | | [13.13.19](epas13_13_19_rel_notes) | 09 Nov 2023 | [13.13](https://www.postgresql.org/docs/release/13.13/) | | [13.12.18](epas13_12_17_rel_notes) | 25 Sep 2023 | | | [13.12.17](epas13_12_17_rel_notes) | 21 Aug 2023 | [13.12](https://www.postgresql.org/docs/release/13.12/) | diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_11_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_11_0_rel_notes.mdx new file mode 100644 index 00000000000..648fe75bf54 --- /dev/null +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_11_0_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 14.11.0 release notes +navTitle: "Version 14.11.0" +--- + +Released: 8 Feb 2024 + +EDB Postgres Advanced Server 14.11.0 includes the following enhancements and bug fixes: + +| Type | Description | Category | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Upstream merge | Merged with community PostgreSQL 14.11. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 14.11 Release Notes](https://www.postgresql.org/docs/release/14.11/) for more information. \ No newline at end of file diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index 4b62d9e7fdb..0a27a139ad0 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas14_11_0_rel_notes - epas14_10_0_rel_notes - epas14_9_1_rel_notes - epas14_9_0_rel_notes @@ -21,6 +22,7 @@ The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation de | Version | Release date | Upstream merges | | --------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------ | +| [14.11.0](epas14_11_0_rel_notes) | 08 Feb 2024 | [14.11](https://www.postgresql.org/docs/14/release-14-11.html) | | [14.10.0](epas14_10_0_rel_notes) | 09 Nov 2023 | [14.10](https://www.postgresql.org/docs/14/release-14-10.html) | | [14.9.1](epas14_9_1_rel_notes) | 25 Sep 2023 | | | [14.9.0](epas14_9_0_rel_notes) | 21 Aug 2023 | [14.9](https://www.postgresql.org/docs/14/release-14-9.html) | diff --git a/product_docs/docs/epas/15/epas_rel_notes/epas15_6_0_rel_notes.mdx b/product_docs/docs/epas/15/epas_rel_notes/epas15_6_0_rel_notes.mdx new file mode 100644 index 00000000000..43289bb2481 --- /dev/null +++ b/product_docs/docs/epas/15/epas_rel_notes/epas15_6_0_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 15.6.0 release notes +navTitle: "Version 15.6.0" +--- + +Released: 8 Feb 2024 + +EDB Postgres Advanced Server 15.6.0 includes the following enhancements and bug fixes: + +| Type | Description | Category | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Upstream merge | Merged with community PostgreSQL 15.6. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 15.6 Release Notes](https://www.postgresql.org/docs/release/15.6/) for more information. \ No newline at end of file diff --git a/product_docs/docs/epas/15/epas_rel_notes/index.mdx b/product_docs/docs/epas/15/epas_rel_notes/index.mdx index fc055d7677d..bbef2bebd7f 100644 --- a/product_docs/docs/epas/15/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/15/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas15_6_0_rel_notes - epas15_5_0_rel_notes - epas15_4_1_rel_notes - epas15_4_0_rel_notes @@ -15,6 +16,7 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | | ------------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| [15.6.0](epas15_6_0_rel_notes) | 08 Feb 2024 | [15.6](https://www.postgresql.org/docs/release/15.6/) | [15.5.0](epas15_5_0_rel_notes) | 09 Nov 2023 | [15.5](https://www.postgresql.org/docs/release/15.5/) | | [15.4.1](epas15_4_1_rel_notes) | 25 Sep 2023 | | | [15.4.0](epas15_4_0_rel_notes) | 21 Aug 2023 | [15.4](https://www.postgresql.org/docs/release/15.4/) | diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx new file mode 100644 index 00000000000..a7af0d05f62 --- /dev/null +++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 16.2 release notes +navTitle: "Version 16.2" +--- + +Released: 8 Feb 2024 + +EDB Postgres Advanced Server 16.2 includes the following enhancements and bug fixes: + +| Type | Description | Category | +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | +| Upstream merge | Merged with community PostgreSQL 16.2. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file diff --git a/product_docs/docs/epas/16/epas_rel_notes/index.mdx b/product_docs/docs/epas/16/epas_rel_notes/index.mdx index b71117fcac1..11057b59f9d 100644 --- a/product_docs/docs/epas/16/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/16/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas16_02_0_rel_notes - epas16_rel_notes --- @@ -12,6 +13,7 @@ The EDB Postgres Advanced Server documentation describes the latest version of E | Version | Release date | Upstream merges | | ------------------------ | ------------ | ---------------------------------------------------------- | +| [16.2](epas16_2_0_rel_notes)| 08 Feb 2024 | [16.2](https://www.postgresql.org/docs/16/release-16-2.html) | [16.1](epas16_rel_notes) | 09 Nov 2023 | [16.0](https://www.postgresql.org/docs/16/release-16.html),[16.1](https://www.postgresql.org/docs/release/16.1/) | ## Component certification diff --git a/product_docs/docs/pge/15/release_notes/index.mdx b/product_docs/docs/pge/15/release_notes/index.mdx index 61bcc07609e..787e1f8320c 100644 --- a/product_docs/docs/pge/15/release_notes/index.mdx +++ b/product_docs/docs/pge/15/release_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - rel_notes15.6 - rel_notes15.5 - rel_notes15.4 - rel_notes15.3 @@ -12,6 +13,7 @@ release notes cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | +| [15.6](rel_notes15.6) | 08 Feb 2024 | | [15.5](rel_notes15.5) | 09 Nov 2023 | | [15.4](rel_notes15.4) | 21 Aug 2023 | | [15.3](rel_notes15.3) | 11 May 2023 | diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.6.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.6.mdx new file mode 100644 index 00000000000..1ff7f4b9f98 --- /dev/null +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.6.mdx @@ -0,0 +1,16 @@ +--- +title: "EDB Postgres Extended Server 15.6 release notes" +navTitle: Version 15.6 +--- + +Released: 8 Feb 2024 + +New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.6 include: + +| Type | Description | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Upstream merge | Merged with community PostgreSQL 15.6. See the [PostgreSQL 15 Release Notes](https://www.postgresql.org/docs/15/release-15-6.html) for more information. | + + + + diff --git a/product_docs/docs/pge/16/release_notes/index.mdx b/product_docs/docs/pge/16/release_notes/index.mdx index 0fc405c51ec..bb7d8c875b8 100644 --- a/product_docs/docs/pge/16/release_notes/index.mdx +++ b/product_docs/docs/pge/16/release_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - rel_notes16.2 - rel_notes16.1 --- The EDB Postgres Extended Server documentation describes the latest version of EDB Postgres Extended Server 16, @@ -9,6 +10,7 @@ cover what was new in each release. | Version | Release date | | ------------------------ | ------------ | +| [16.2](rel_notes16.2) | 08 Feb 2024 | | [16.1](rel_notes16.1) | 09 Nov 2023 | diff --git a/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx b/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx new file mode 100644 index 00000000000..f3aa30cba1c --- /dev/null +++ b/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx @@ -0,0 +1,12 @@ +--- +title: EDB Postgres Advanced Server 16.2 release notes +navTitle: "Version 16.2" +--- + +Released: 8 Feb 2024 + +EDB Postgres Extended Server 16.2 includes the following enhancements and bug fixes: + +| Type | Description +| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- +| Upstream merge | Merged with community PostgreSQL 16.2. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file From ec81e05432a8392cdcf2714623d23c8f58f585a4 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Sat, 10 Feb 2024 14:16:32 +0000 Subject: [PATCH 21/22] Late change Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pge/15/release_notes/rel_notes15.5.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pge/15/release_notes/rel_notes15.5.mdx b/product_docs/docs/pge/15/release_notes/rel_notes15.5.mdx index 6215fc5b510..ff1c3567b94 100644 --- a/product_docs/docs/pge/15/release_notes/rel_notes15.5.mdx +++ b/product_docs/docs/pge/15/release_notes/rel_notes15.5.mdx @@ -5,7 +5,7 @@ navTitle: Version 15.5 Released: 9 Nov 2023 -New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.2 include: +New features, enhancements, bug fixes, and other changes in EDB Postgres Extended Server 15.5 include: | Type | Description | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | From b4d55a389eb91ad62794805dbd9042f0fdb50f60 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 12 Feb 2024 16:16:22 +0000 Subject: [PATCH 22/22] Adjusted for CVE status on 16. Signed-off-by: Dj Walker-Morgan --- .../docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx | 2 +- product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx index a7af0d05f62..d4980a2eed6 100644 --- a/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx +++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx @@ -9,4 +9,4 @@ EDB Postgres Advanced Server 16.2 includes the following enhancements and bug fi | Type | Description | Category | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -| Upstream merge | Merged with community PostgreSQL 16.2. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file +| Upstream merge | Merged with community PostgreSQL 16.2. Important: Although not vulnerable to the recent 8.0 scoring CVE, CVE-2024-0985, this release includes tightened security restrictions which address the same issues. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file diff --git a/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx b/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx index f3aa30cba1c..395e8efcf90 100644 --- a/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx +++ b/product_docs/docs/pge/16/release_notes/rel_notes16.2.mdx @@ -9,4 +9,4 @@ EDB Postgres Extended Server 16.2 includes the following enhancements and bug fi | Type | Description | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -| Upstream merge | Merged with community PostgreSQL 16.2. Important: this release includes a CVE with a score of 8.0. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file +| Upstream merge | Merged with community PostgreSQL 16.2. Important: Although not vulnerable to the recent 8.0 scoring CVE, CVE-2024-0985, this release includes tightened security restrictions which address the same issues. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information. \ No newline at end of file