From 758320cf1b184382f02469c38778564c59b3b817 Mon Sep 17 00:00:00 2001 From: francoughlin Date: Mon, 11 Sep 2023 12:13:10 -0400 Subject: [PATCH 01/19] BigAnimal: CLI updates for 3.0 --- .../reference/cli/managing_clusters.mdx | 36 ++++++++++--------- 1 file changed, 20 insertions(+), 16 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 7e51a2e4c86..b59de7aed16 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -4,7 +4,9 @@ navTitle: Managing clusters deepToC: true --- -These examples show Azure as the cloud provider unless indicated otherwise. The functionality is the same when using AWS or Google Cloud. +These examples show Azure as the cloud provider unless indicated otherwise. + +Although the functionality is the same when using AWS or Google Cloud, there may be additional input flags based on cloud provider type. Use the `-h` or `--help` flags for more information on the CLI commands. ## Managing single-node and primary/standby high-availability clusters @@ -126,15 +128,15 @@ To enable you to view valid values to use in the configuration file for BigAnima ```shell biganimal cluster show-architectures __OUTPUT__ -┌───────────────────────────────────────────────┐ -│ Architecture │ -├────────┬───────────────────────────┬──────────┤ -│ ID │ Name │ Status │ -├────────┼───────────────────────────┼──────────┤ -│ ha │ High Availability │ enabled │ -│ pgd │ Extreme High Availability │ disabled │ -│ single │ Single Node │ enabled │ -└────────┴───────────────────────────┴──────────┘ +┌───────────────────────────────────────────────────────────────┐ +│ Architecture │ +├────────┬───────────────────────────────────────────┬──────────┤ +│ ID │ Name │ Status │ +├────────┼───────────────────────────────────────────┼──────────┤ +│ ha │ Primary/Standby High Availability │ enabled │ +│ pgd │ Distributed High Availability │ disabled │ +│ single │ Single Node │ enabled │ +└────────┴───────────────────────────────────────────┴──────────┘ ``` !!!Tip @@ -151,12 +153,14 @@ biganimal cluster show-connection \ --provider "azure" \ --region "eastus" __OUTPUT__ -┌─────────────┬──────────────────────────────────────────────────────────────────────────────────────────┐ -│ Access Type │ Connection String │ -├─────────────┼──────────────────────────────────────────────────────────────────────────────────────────┤ -│ read-write │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ -│ read-only │ Disabled │ -└─────────────┴──────────────────────────────────────────────────────────────────────────────────────────┘ +┌─────────────────┬──────────────────────────────────────────────────────────────────────────────────────────┐ +│ Name │ Details │ +├─────────────────┼──────────────────────────────────────────────────────────────────────────────────────────┤ +│ read-write │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ +│ rw-service-name │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ +│ read-only │ Disabled │ +│ ro-service-name │ Disabled │ +└─────────────────┴──────────────────────────────────────────────────────────────────────────────────────────┘ ``` !!!tip From 1304e5d0d79bc441bbc48d264c31080cfa379618 Mon Sep 17 00:00:00 2001 From: Fran Coughlin <132373434+francoughlin@users.noreply.github.com> Date: Tue, 12 Sep 2023 08:49:26 -0400 Subject: [PATCH 02/19] Update product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx Co-authored-by: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> --- .../docs/biganimal/release/reference/cli/managing_clusters.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index b59de7aed16..9df844747b2 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -6,7 +6,7 @@ deepToC: true These examples show Azure as the cloud provider unless indicated otherwise. -Although the functionality is the same when using AWS or Google Cloud, there may be additional input flags based on cloud provider type. Use the `-h` or `--help` flags for more information on the CLI commands. +Although the functionality is the same when using AWS or Google Cloud, there may be additional input flags based on the cloud provider type. Use the `-h` or `--help` flags for more information on the CLI commands. ## Managing single-node and primary/standby high-availability clusters From a4785c4be54fc7e07897a375fce1e7cfa2f8a111 Mon Sep 17 00:00:00 2001 From: francoughlin Date: Tue, 12 Sep 2023 09:10:31 -0400 Subject: [PATCH 03/19] Updated cluster names per review comment --- .../biganimal/release/reference/cli/managing_clusters.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 9df844747b2..26cb9155504 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -133,8 +133,8 @@ __OUTPUT__ ├────────┬───────────────────────────────────────────┬──────────┤ │ ID │ Name │ Status │ ├────────┼───────────────────────────────────────────┼──────────┤ -│ ha │ Primary/Standby High Availability │ enabled │ -│ pgd │ Distributed High Availability │ disabled │ +│ ha │ High Availability │ enabled │ +│ pgd │ Extreme High Availability │ disabled │ │ single │ Single Node │ enabled │ └────────┴───────────────────────────────────────────┴──────────┘ ``` From 51e41b7e33d807029f3bd64689e6e2730bbecad0 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 10 Oct 2023 10:28:09 -0400 Subject: [PATCH 04/19] Update managing_clusters.mdx --- .../biganimal/release/reference/cli/managing_clusters.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 26cb9155504..39ffd0edeb3 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -25,7 +25,7 @@ For example, to create a primary/standby high-availability cluster: ```shell biganimal cluster create __OUTPUT__ -Cluster architecture: High Availability +Cluster architecture: Primary/Standby High Availability Number of standby replicas: 2 Replicas Enable read-only workloads: No Provider: Azure @@ -82,7 +82,7 @@ Here's a sample configuration file in YAML format with Azure specified as the pr # config_file.yaml --- clusterArchitecture: ha # - haStandbyReplicas: 2 # + haStandbyReplicas: 2 # provider: azure # clusterName: my-biganimal-cluster # password: ************ # @@ -133,7 +133,7 @@ __OUTPUT__ ├────────┬───────────────────────────────────────────┬──────────┤ │ ID │ Name │ Status │ ├────────┼───────────────────────────────────────────┼──────────┤ -│ ha │ High Availability │ enabled │ +│ ha │ Primary/Standby High Availability │ enabled │ │ pgd │ Extreme High Availability │ disabled │ │ single │ Single Node │ enabled │ └────────┴───────────────────────────────────────────┴──────────┘ From 6ae16dc0ec246ec5d7aff0d55af86de49c532770 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 17 Oct 2023 13:17:04 -0400 Subject: [PATCH 05/19] Update managing_clusters.mdx --- .../release/reference/cli/managing_clusters.mdx | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 39ffd0edeb3..ba49257f8b0 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -153,14 +153,14 @@ biganimal cluster show-connection \ --provider "azure" \ --region "eastus" __OUTPUT__ -┌─────────────────┬──────────────────────────────────────────────────────────────────────────────────────────┐ -│ Name │ Details │ -├─────────────────┼──────────────────────────────────────────────────────────────────────────────────────────┤ -│ read-write │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ -│ rw-service-name │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ -│ read-only │ Disabled │ -│ ro-service-name │ Disabled │ -└─────────────────┴──────────────────────────────────────────────────────────────────────────────────────────┘ +┌───────────────-----------──┬──────────────────────────────────────────────────────────────────────────────────────────┐ +│ Name │ Details │ +├────────────────-----------─┼──────────────────────────────────────────────────────────────────────────────────────────┤ +│ read-write-connection │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ +│ rw-service-name │ postgresql://edb_admin@p-gxhkfww1fe.30glixgayvwhtmn3.enterprisedb.network:5432/edb_admin │ +│ read-only-connection │ Disabled │ +│ ro-service-name │ Disabled │ +└─────────────────-----------┴──────────────────────────────────────────────────────────────────────────────────────────┘ ``` !!!tip From 944b82afb369ea798d67d92234b1e3c78f33773b Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 17 Oct 2023 15:25:41 -0400 Subject: [PATCH 06/19] Updated per Amol's comments --- .../release/reference/cli/managing_clusters.mdx | 12 ++++++++++++ .../release/reference/cli/using_features.mdx | 12 ++++++++++++ 2 files changed, 24 insertions(+) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index ba49257f8b0..0c5a2b3b8d6 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -29,6 +29,12 @@ Cluster architecture: Primary/Standby High Availability Number of standby replicas: 2 Replicas Enable read-only workloads: No Provider: Azure +Cloud provider subscription ID: +- 123123123 +- 456456456 +Service account IDs: +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com Cluster Name: my-biganimal-cluster Password: **************** PostgreSQL type: EDB Postgres Advanced Server @@ -192,6 +198,8 @@ After the cluster is created, you can update attributes of the cluster, includin - Retention period - Read-only workloads - IAM authentication +- Cloud service provider subscription IDs +- Service account IDs For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: @@ -268,6 +276,10 @@ biganimal cluster restore\ --restore-point "2022-01-26T15:04:05+0800" \ --backup-retention-period "2w" \ --read-only-workloads: "true" + --csp-subscription-ids "123123123,456456456" + --service-account-ids "service-account-1234567b@development-data-123456.iam.gserviceaccount.com, +service-account-1234567b@development-data-123456.iam.gserviceaccount.com" + --credential "my_credential" ``` The password for the restored cluster is mandatory. The other parameters, if not specified, inherit the source database's settings. diff --git a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx index 9430e081012..569733cd64d 100644 --- a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx @@ -24,6 +24,12 @@ __OUTPUT__ ? Volume type: Azure Premium Storage ? Volume properties: P1 (4 Gi, 120 Provisioned IOPS, 25 Provisioned MB/s) ? Networking: Public +? Cloud Provider Subscription ID: +- 123123123 +- 456456456 +? Service Account IDs, (leave empty to stop adding): +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com ? By default your cluster allows all inbound communications, add IP allowed list to restrict the access: No ? Add database config in the format "application_name=sample_app&array_nulls=true", Leave empty for default configuration: ? Backup Retention Period, note backups will incur storage charges from the cloud provider directly. e.g. "7d", "2w" or "3m": 3m @@ -70,6 +76,12 @@ __OUTPUT__ ? Volume properties: P1 (4 Gi, 120 Provisioned IOPS, 25 Provisioned MB/s) ? Networking: Public ? By default your cluster allows all inbound communications, add IP allowed list to restrict the access: No +? Cloud Provider Subscription ID: +- 123123123 +- 456456456 +? Service Account IDs, (leave empty to stop adding): +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +- service-account-1234567b@development-data-123456.iam.gserviceaccount.com ? Add database config in format "application_name=sample_app&array_nulls=true": autovacuum_max_workers=5&autovacuum_vacuum_cost_limit=3000&checkpoint_completion_target=0.9&checkpoint_timeout=15min&cpu_tuple_cost=0.03&effective_cache_size=0.75 * ram&maintenance_work_mem=(0.15 * (ram - shared_buffers) / autovacuum_max_workers) > 1GB ? 1GB : (0.15 * (ram - shared_buffers) / autovacuum_max_workers)&random_page_cost=1.1&shared_buffers=((0.25 * ram) > 80GB) ? 80GB : (0.25 * ram)&tcp_keepalives_idle=120&tcp_keepalives_interval=30&wal_buffers=64MB&wal_compression=on ? Backup Retention Period, use strings like '7d' or '2w' or '3m' to specify days, weeks and months respectively.: 3m ``` From 9abc843bbf19183841b2d72f4642e7c34bd735f9 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 2 Nov 2023 11:23:24 -0400 Subject: [PATCH 07/19] Update managing_clusters.mdx --- .../biganimal/release/reference/cli/managing_clusters.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index 0c5a2b3b8d6..05f88641330 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -29,12 +29,8 @@ Cluster architecture: Primary/Standby High Availability Number of standby replicas: 2 Replicas Enable read-only workloads: No Provider: Azure -Cloud provider subscription ID: -- 123123123 -- 456456456 -Service account IDs: -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +Cloud Provider Subscription ID: "111,222" +Service Account IDs, (leave empty to stop adding): "id1@iam.gcp" Cluster Name: my-biganimal-cluster Password: **************** PostgreSQL type: EDB Postgres Advanced Server From 2ec04f41efe6918dd1ed9ddff51b71679ab60fba Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Thu, 2 Nov 2023 11:25:47 -0400 Subject: [PATCH 08/19] Update using_features.mdx --- .../biganimal/release/reference/cli/using_features.mdx | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx index 569733cd64d..603018f7e5d 100644 --- a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx @@ -76,12 +76,8 @@ __OUTPUT__ ? Volume properties: P1 (4 Gi, 120 Provisioned IOPS, 25 Provisioned MB/s) ? Networking: Public ? By default your cluster allows all inbound communications, add IP allowed list to restrict the access: No -? Cloud Provider Subscription ID: -- 123123123 -- 456456456 -? Service Account IDs, (leave empty to stop adding): -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +? Cloud Provider Subscription ID: "111,222" +? Service Account IDs, (leave empty to stop adding): "id1@iam.gcp" ? Add database config in format "application_name=sample_app&array_nulls=true": autovacuum_max_workers=5&autovacuum_vacuum_cost_limit=3000&checkpoint_completion_target=0.9&checkpoint_timeout=15min&cpu_tuple_cost=0.03&effective_cache_size=0.75 * ram&maintenance_work_mem=(0.15 * (ram - shared_buffers) / autovacuum_max_workers) > 1GB ? 1GB : (0.15 * (ram - shared_buffers) / autovacuum_max_workers)&random_page_cost=1.1&shared_buffers=((0.25 * ram) > 80GB) ? 80GB : (0.25 * ram)&tcp_keepalives_idle=120&tcp_keepalives_interval=30&wal_buffers=64MB&wal_compression=on ? Backup Retention Period, use strings like '7d' or '2w' or '3m' to specify days, weeks and months respectively.: 3m ``` @@ -132,4 +128,4 @@ biganimal cluster [set|get]-maintenance-window {--enable} [--start-day --start-time] ``` -For more information on maintenance windows, see [Periodic maintenance](/biganimal/release/overview/updates). \ No newline at end of file +For more information on maintenance windows, see [Periodic maintenance](/biganimal/release/overview/updates). From 7a0701d463960c4498e86a39e1a82c3a6b910b71 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 7 Nov 2023 12:53:04 -0500 Subject: [PATCH 09/19] Update using_features.mdx --- .../biganimal/release/reference/cli/using_features.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx index 603018f7e5d..cc44bc95be2 100644 --- a/product_docs/docs/biganimal/release/reference/cli/using_features.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/using_features.mdx @@ -24,12 +24,8 @@ __OUTPUT__ ? Volume type: Azure Premium Storage ? Volume properties: P1 (4 Gi, 120 Provisioned IOPS, 25 Provisioned MB/s) ? Networking: Public -? Cloud Provider Subscription ID: -- 123123123 -- 456456456 -? Service Account IDs, (leave empty to stop adding): -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com -- service-account-1234567b@development-data-123456.iam.gserviceaccount.com +? Cloud Provider Subscription ID: "111,222" +? Service Account IDs, (leave empty to stop adding): "id1@iam.gcp" ? By default your cluster allows all inbound communications, add IP allowed list to restrict the access: No ? Add database config in the format "application_name=sample_app&array_nulls=true", Leave empty for default configuration: ? Backup Retention Period, note backups will incur storage charges from the cloud provider directly. e.g. "7d", "2w" or "3m": 3m From 271c31901b14f5f24f1cfcf0588ae9eee176399d Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 9 Nov 2023 18:30:07 +0000 Subject: [PATCH 10/19] Update installer metadata; update links and version numbers --- install_template/config.yaml | 34 +++++++++---------- .../16/02_requirements_overview.mdx | 15 ++++---- product_docs/docs/odbc_connector/16/index.mdx | 2 +- 3 files changed, 26 insertions(+), 25 deletions(-) diff --git a/install_template/config.yaml b/install_template/config.yaml index 9ff71354c48..7c8bab630e1 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -162,55 +162,55 @@ products: platforms: - name: CentOS 7 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: RHEL 8 arch: ppc64le - supported versions: [13] + supported versions: [13, 16] - name: RHEL 9 arch: ppc64le - supported versions: [13] + supported versions: [13, 16] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: RHEL 7 or OL 7 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: Debian 10 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: Debian 11 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: Ubuntu 18.04 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: SLES 12 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: SLES 12 arch: ppc64le - supported versions: [13] + supported versions: [13, 16] - name: SLES 15 arch: x86_64 - supported versions: [13] + supported versions: [13, 16] - name: SLES 15 arch: ppc64le - supported versions: [13] + supported versions: [13, 16] - name: EDB pgBouncer platforms: - name: CentOS 7 diff --git a/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx b/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx index ccec4fd622b..8b5747f586e 100644 --- a/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx +++ b/product_docs/docs/odbc_connector/16/02_requirements_overview.mdx @@ -9,10 +9,11 @@ The ODBC Connector is supported on the same platforms as EDB Postgres Advanced S This table lists the latest ODBC Connector versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. -| ODBC Connector | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | -| ----------------------------------------------------------- | ------- | ------- | ------- | ------- | ------- | -| [13.02.0.02](01_odbc_rel_notes/odbc_13.2.0.02_rel_notes) | Y | Y | Y | Y | Y | -| [13.02.0.01](01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes) | N | Y | Y | Y | Y | -| [13.01.0.02](01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes) | N | Y | Y | Y | Y | -| [13.01.0.01](01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes) | N | N | Y | Y | Y | -| [13.00.0.01](01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes) | N | N | Y | Y | Y | \ No newline at end of file +| ODBC Connector | EPAS 16 | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | +| ------------------------------------------------------------------------------ | ------- | ------- | ------- | ------- | ------- | ------- | +| [16.00.0000.01](01_odbc_rel_notes/odbc_16.00.00000.01_rel_notes) | Y | Y | Y | Y | Y | Y | +| [13.02.0.02](/odbc_connector/13/01_odbc_rel_notes/odbc_13.2.0.02_rel_notes) | N | Y | Y | Y | Y | Y | +| [13.02.0.01](/odbc_connector/13/01_odbc_rel_notes/02_odbc_13.2.0.01_rel_notes) | N | N | Y | Y | Y | Y | +| [13.01.0.02](/odbc_connector/13/01_odbc_rel_notes/03_odbc_13.1.0.02_rel_notes) | N | N | Y | Y | Y | Y | +| [13.01.0.01](/odbc_connector/13/01_odbc_rel_notes/04_odbc_13.1.0.01_rel_notes) | N | N | N | Y | Y | Y | +| [13.00.0.01](/odbc_connector/13/01_odbc_rel_notes/05_odbc_13.0.0.01_rel_notes) | N | N | N | Y | Y | Y | \ No newline at end of file diff --git a/product_docs/docs/odbc_connector/16/index.mdx b/product_docs/docs/odbc_connector/16/index.mdx index 532a1bbe899..a73d8756bf7 100644 --- a/product_docs/docs/odbc_connector/16/index.mdx +++ b/product_docs/docs/odbc_connector/16/index.mdx @@ -1,7 +1,7 @@ --- title: "EDB ODBC Connector" directoryDefaults: - description: "EDB ODBC Connector Version 12.2.0.2 Documentation and release notes." + description: "EDB ODBC Connector documentation and release notes." redirects: - 03_edb-odbc_overview/ navigation: From 7f9946e8425219be691f488fb0d51743a58ccd64 Mon Sep 17 00:00:00 2001 From: Josh Heyer Date: Thu, 9 Nov 2023 18:30:19 +0000 Subject: [PATCH 11/19] Generated installer files --- .../2/installing/linux_x86_64/mysql_debian_10.mdx | 2 +- product_docs/docs/odbc_connector/16/installing/index.mdx | 8 ++++---- .../16/installing/linux_ppc64le/odbc_rhel_8.mdx | 2 +- .../16/installing/linux_ppc64le/odbc_rhel_9.mdx | 2 +- .../16/installing/linux_ppc64le/odbc_sles_12.mdx | 2 +- .../16/installing/linux_ppc64le/odbc_sles_15.mdx | 2 +- .../16/installing/linux_x86_64/odbc_centos_7.mdx | 2 +- .../16/installing/linux_x86_64/odbc_debian_10.mdx | 2 +- .../16/installing/linux_x86_64/odbc_debian_11.mdx | 2 +- .../16/installing/linux_x86_64/odbc_other_linux_8.mdx | 2 +- .../16/installing/linux_x86_64/odbc_other_linux_9.mdx | 2 +- .../16/installing/linux_x86_64/odbc_rhel_7.mdx | 2 +- .../16/installing/linux_x86_64/odbc_rhel_8.mdx | 2 +- .../16/installing/linux_x86_64/odbc_rhel_9.mdx | 2 +- .../16/installing/linux_x86_64/odbc_sles_12.mdx | 2 +- .../16/installing/linux_x86_64/odbc_sles_15.mdx | 2 +- .../16/installing/linux_x86_64/odbc_ubuntu_18.mdx | 2 +- .../16/installing/linux_x86_64/odbc_ubuntu_20.mdx | 2 +- .../16/installing/linux_x86_64/odbc_ubuntu_22.mdx | 2 +- 19 files changed, 22 insertions(+), 22 deletions(-) diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx index 6b5231ae149..d553f46ea8f 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_x86_64/mysql_debian_10.mdx @@ -39,7 +39,7 @@ Before you begin the installation process: 1. Follow the instructions for setting up the EDB repository. -- Download the GPG key to your APT keyring directly using the apt-key utility: +- Download the GPG key to your APT keyring directly using the apt-key utility ```shell sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 3A79BD29 ``` diff --git a/product_docs/docs/odbc_connector/16/installing/index.mdx b/product_docs/docs/odbc_connector/16/installing/index.mdx index 822069c7cad..5fa733d40dd 100644 --- a/product_docs/docs/odbc_connector/16/installing/index.mdx +++ b/product_docs/docs/odbc_connector/16/installing/index.mdx @@ -8,10 +8,10 @@ title: Installing EDB ODBC Connector redirects: - ../03_edb-odbc_overview/01_installing_edb-odbc - - /odbc_connector/13/03_installing_edb_odbc/ - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/07_odbc13_ubuntu20_deb10_x86/ - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/ + - /odbc_connector/16/03_installing_edb_odbc/ + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/07_odbc13_ubuntu20_deb10_x86/ + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/12_odbc13_sles12_ppcle/ navigation: - linux_x86_64 diff --git a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_8.mdx index 43763848216..5b6f43c542b 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 8 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel8_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_9.mdx index 0bb9aab169a..e5dd0cc81bb 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_9.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 9 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel9_ppcle + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_rhel9_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_12.mdx index eadd467df54..4806c6d2886 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 12 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles12_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_15.mdx index ac20d9f0696..076567562f3 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_ppc64le/odbc_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 15 ppc64le # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/ibm_power_ppc64le/odbc13_sles15_ppcle --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_centos_7.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_centos_7.mdx index b6d97d5a3a4..89d79ecf403 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_centos_7.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_centos_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on CentOS 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_centos7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_10.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_10.mdx index c4a97d2488a..4a98f15cefd 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_10.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_10.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Debian 10 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb10_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_11.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_11.mdx index 97225a3a6ca..71fbb61b637 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_11.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_debian_11.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Debian 11 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_deb11_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_8.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_8.mdx index 918cf6ef710..8371039d659 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_8.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on AlmaLinux 8 or Rocky Linux 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_9.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_9.mdx index 77d9049ea8c..006e8ac89c2 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_9.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_other_linux_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on AlmaLinux 9 or Rocky Linux 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux9_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_other_linux9_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_7.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_7.mdx index 7f559cef450..f6f491b2019 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_7.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_7.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 7 or OL 7 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel7_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_8.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_8.mdx index 2d99bb0458a..63816ff1a42 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_8.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_8.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 8 or OL 8 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel8_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_9.mdx index b2a9237eaed..6cb229ab1c6 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_9.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_rhel_9.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on RHEL 9 or OL 9 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel9_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_rhel9_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_12.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_12.mdx index 036e4128907..72d30084492 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_12.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_12.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 12 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles12_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_15.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_15.mdx index cca6bf4b2ff..323e084d854 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_15.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_sles_15.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on SLES 15 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_sles15_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_18.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_18.mdx index f1a0276bace..faea0b8f02a 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_18.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_18.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Ubuntu 18.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu18_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_20.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_20.mdx index 74196019ffd..1c369f73e4a 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_20.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_20.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Ubuntu 20.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu20_x86 --- ## Prerequisites diff --git a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_22.mdx b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_22.mdx index b780e704aac..b4f635e8d5b 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_22.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_x86_64/odbc_ubuntu_22.mdx @@ -6,7 +6,7 @@ title: Installing EDB ODBC Connector on Ubuntu 22.04 x86_64 # the documentation team will update the templates accordingly. redirects: - - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu22_x86 + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/x86_amd64/odbc13_ubuntu22_x86 --- ## Prerequisites From aa5a767eef4e7630097d763e06a2ad0623e18249 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Tue, 14 Nov 2023 15:33:13 +0000 Subject: [PATCH 12/19] Release notes TPA 23.25 --- product_docs/docs/tpa/23/rel_notes/index.mdx | 2 ++ .../tpa/23/rel_notes/tpa_23.25_rel_notes.mdx | 23 +++++++++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx index 8be8fac3392..79f1b03551c 100644 --- a/product_docs/docs/tpa/23/rel_notes/index.mdx +++ b/product_docs/docs/tpa/23/rel_notes/index.mdx @@ -2,6 +2,7 @@ title: Trusted Postgres Architect release notes navTitle: "Release notes" navigation: + - tpa_23.25_rel_notes - tpa_23.24_rel_notes - tpa_23.23_rel_notes - tpa_23.22_rel_notes @@ -22,6 +23,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru | Version | Release date | | ---------------------------- | ------------ | +| [23.25](tpa_23.25_rel_notes) | 14 Nov 2023 | | [23.24](tpa_23.24_rel_notes) | 17 Oct 2023 | | [23.23](tpa_23.23_rel_notes) | 21 Sep 2023 | | [23.22](tpa_23.22_rel_notes) | 06 Sep 2023 | diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx new file mode 100644 index 00000000000..eed345cb518 --- /dev/null +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx @@ -0,0 +1,23 @@ +--- +title: Trusted Postgres Architect 23.25 release notes +navTitle: "Version 23.25" +--- + +Released: 14 Nov 2023 + +New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.25 include the following: + +| Type | Description | +| ---- |------------ | +| Enhancement | TPA now supports automated upgrades from PGD 3.7 to PGD 5.3 or above. | +| Enhancement | TPA now supports EDB Advanced Server 16 and EDB Extended Server 16. | +| Change | Various improvements to the upgrade process introduced with PGD 4 to PGD 5 upgrades have been backported to BDR-Always-ON upgrades. | +| Change | TPA now supports installing PEM on SLES. | +| Change | TPA now explicitly sets permissions when creating some filesystem objects. This will be extended to all filesystem objects in a future release. | +| Change | TPA now adds a symlink to the pgd-cli config file for v1 so it can be run without having to specify the path via `-f` switch. | +| Change | TPA now calls the `alter_node_kind` PGD function to ensure node kind is set correctly for BDR-Always-ON clusters using BDR version 4.3 and above. | +| Change | Default cluster configuration from now selects SLES 15 SP5 when SLES 15 is requested (previously SP4). | +| Bug Fix | Fixed an issue which resulted in a checksum failure during `tpaexec setup` command for tpaexec-deps users. | +| Bug Fix | Fixed an issue whereby `pem_server_group` was not correctly applied when pemworker was invoked meaning servers were not grouped as expected in PEM. | +| Bug Fix | Fixed an issue with the sys/sysstat role whereby `sar` was not scheduled to run on instances other than the Barman instance. | + From 3f78ef35395d2d50601ab1907ee42b970360aa02 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Tue, 14 Nov 2023 15:34:43 +0000 Subject: [PATCH 13/19] Add note regarding CAMO support --- product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx index eed345cb518..8e9645f8697 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.25_rel_notes.mdx @@ -9,7 +9,7 @@ New features, enhancements, bug fixes, and other changes in Trusted Postgres Arc | Type | Description | | ---- |------------ | -| Enhancement | TPA now supports automated upgrades from PGD 3.7 to PGD 5.3 or above. | +| Enhancement | TPA now supports automated upgrades from PGD 3.7 to PGD 5.3 or above. *Note, upgrading clusters with CAMO is not yet supported.* | | Enhancement | TPA now supports EDB Advanced Server 16 and EDB Extended Server 16. | | Change | Various improvements to the upgrade process introduced with PGD 4 to PGD 5 upgrades have been backported to BDR-Always-ON upgrades. | | Change | TPA now supports installing PEM on SLES. | From fd5bed544919e068bb64215779b82a7106d8d9be Mon Sep 17 00:00:00 2001 From: sszhao1020 <89435179+sszhao1020@users.noreply.github.com> Date: Thu, 19 Oct 2023 19:55:45 +0800 Subject: [PATCH 14/19] Update managing_clusters.mdx updated the sample of config_file.yaml with the latest version. With the issues we got here https://edb.slack.com/archives/C02UY58G6HJ/p1697712863949449 --- .../reference/cli/managing_clusters.mdx | 63 ++++++++++--------- 1 file changed, 35 insertions(+), 28 deletions(-) diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx index c7a8f2ffa85..63a1fb6a8aa 100644 --- a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx +++ b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx @@ -77,34 +77,41 @@ You can use the `create --config-file` command to create one or more clusters wi Here's a sample configuration file in YAML format with Azure specified as the provider: ```yaml - # config_file.yaml - --- - clusterArchitecture: ha # - haStandbyReplicas: 2 # - provider: azure # - clusterName: my-biganimal-cluster # - password: ************ # - iamAuthentication: false # - postgresType: epas # - postgresVersion: "14" # - region: eastus # - instanceType: azure:Standard_E2s_v3 # - volumeType: azurepremiumstorage # - volumeProperties: P1 # - volumePropertySize: "4Gi" # - volumePropertyIOPS: 3000 # : Applicable to AWS gp3 and Azure Ultradisk, volume Input/Output Operations Per Second> - networking: public # - allowIpRangeMap: # - - cidr: 9.9.9.9/28 # - description: Allow traffic from App A # - - cidr: 10.10.10.10/27 # - description: Allow traffic from App B # - pgConfigMap: # - application_name: test_app # - array_nulls: true # - backupRetentionPeriod: 30d # - readOnlyWorkloads: # - --- +# config_file.yaml +--- +clusterArchitecture: ha # +haStandbyReplicas: 2 # +provider: azure # +cspSubscriptionIDs: # + - 123123123 # + - 456456456 # +serviceAccountIds: # + - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# + - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# +clusterName: biganimal_cluster # +password: ************ # +# refer following link for steps to setup IAM: https://www.enterprisedb.com/docs/biganimal/latest/using_cluster/01_postgres_access/iam-authentication-for-postgres +iamAuthentication: true # +postgresType: epas # +postgresVersion: 14 # +region: eastus # +instanceType: azure:Standard_E2s_v3 # +volumeType: azurepremiumstorage # +volumeProperties: P1 # +volumePropertySize: 4Gi # +volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> +networking: public # +allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # +readOnlyWorkloads: true # +pgConfigMap: # + application_name: test_app # + array_nulls: true # +backupRetentionPeriod: 30d # +--- ``` !!! Note From 76fbcb0d41ac27d7405446ad22c313c1ad3eed49 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 14 Nov 2023 17:34:25 +0000 Subject: [PATCH 15/19] Imported content Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/INSTALL-repo.mdx | 1 - product_docs/docs/tpa/23/INSTALL.mdx | 4 +--- product_docs/docs/tpa/23/ansible-and-sudo.mdx | 2 +- product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx | 1 - product_docs/docs/tpa/23/firstclusterdeployment.mdx | 1 - .../docs/tpa/23/reference/2q_and_edb_repositories.mdx | 1 - product_docs/docs/tpa/23/reference/air-gapped.mdx | 6 ++---- product_docs/docs/tpa/23/reference/git-credentials.mdx | 1 - product_docs/docs/tpa/23/reference/local-repo.mdx | 3 --- product_docs/docs/tpa/23/tpaexec-upgrade.mdx | 2 +- 10 files changed, 5 insertions(+), 17 deletions(-) diff --git a/product_docs/docs/tpa/23/INSTALL-repo.mdx b/product_docs/docs/tpa/23/INSTALL-repo.mdx index 28f1ac0ce2a..b250a6d7a4a 100644 --- a/product_docs/docs/tpa/23/INSTALL-repo.mdx +++ b/product_docs/docs/tpa/23/INSTALL-repo.mdx @@ -9,7 +9,6 @@ This document explains how to use TPA from a copy of the source code repository. !!! Note - EDB customers must [install TPA from packages](INSTALL/) in order to receive EDB support for the software. diff --git a/product_docs/docs/tpa/23/INSTALL.mdx b/product_docs/docs/tpa/23/INSTALL.mdx index 0faa32c8cf8..bef60e6745a 100644 --- a/product_docs/docs/tpa/23/INSTALL.mdx +++ b/product_docs/docs/tpa/23/INSTALL.mdx @@ -15,8 +15,7 @@ install TPA from source, please refer to See [Distribution support](reference/distributions/) for information on what platforms are supported. -!!! Info - +!!! Important Please make absolutely sure that your system has the correct date and time set, because various things will fail otherwise. We recommend you use a network time, for example `sudo ntpdate @@ -130,7 +129,6 @@ Next, run `tpaexec setup` to create an isolated Python environment and install the correct versions of all required modules. !!! Note - On Ubuntu versions prior to 20.04, please use `sudo -H tpaexec setup` to avoid subsequent permission errors during `tpaexec configure` diff --git a/product_docs/docs/tpa/23/ansible-and-sudo.mdx b/product_docs/docs/tpa/23/ansible-and-sudo.mdx index f5f4ddbe956..18a6be0d309 100644 --- a/product_docs/docs/tpa/23/ansible-and-sudo.mdx +++ b/product_docs/docs/tpa/23/ansible-and-sudo.mdx @@ -1,5 +1,5 @@ --- -title: 'TPA, Ansible, and sudo' +title: TPA, Ansible, and sudo originalFilePath: ansible-and-sudo.md --- diff --git a/product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx b/product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx index c5a98f0ce51..95feae18deb 100644 --- a/product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx +++ b/product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx @@ -79,7 +79,6 @@ regions, your own data centres, or any other designation to identify where your servers are hosted. !!! Note for AWS users - If you are using TPA to provision an AWS cluster, the locations will be mapped to separate availability zones within the `--region` you specify. diff --git a/product_docs/docs/tpa/23/firstclusterdeployment.mdx b/product_docs/docs/tpa/23/firstclusterdeployment.mdx index 3656599e79a..5dcd032f757 100644 --- a/product_docs/docs/tpa/23/firstclusterdeployment.mdx +++ b/product_docs/docs/tpa/23/firstclusterdeployment.mdx @@ -63,7 +63,6 @@ sudo reboot ``` !!! Warning - Giving a user the ability to speak to the Docker daemon lets them trivially gain root on the Docker host. Only trusted users should have access to the Docker daemon. diff --git a/product_docs/docs/tpa/23/reference/2q_and_edb_repositories.mdx b/product_docs/docs/tpa/23/reference/2q_and_edb_repositories.mdx index dd191b340ed..f98c5f1df6b 100644 --- a/product_docs/docs/tpa/23/reference/2q_and_edb_repositories.mdx +++ b/product_docs/docs/tpa/23/reference/2q_and_edb_repositories.mdx @@ -33,7 +33,6 @@ that you have [exported the token](#authenticating-with-package-sources) before running `tpaexec deploy` or the operation will fail. !!! Note - EDB is in the process of publishing all software through Repos 2.0, and will eventually remove the older repositories. diff --git a/product_docs/docs/tpa/23/reference/air-gapped.mdx b/product_docs/docs/tpa/23/reference/air-gapped.mdx index 647e570ee23..4a80131fc49 100644 --- a/product_docs/docs/tpa/23/reference/air-gapped.mdx +++ b/product_docs/docs/tpa/23/reference/air-gapped.mdx @@ -19,7 +19,6 @@ follow the instructions below to either copy an existing cluster configuration or create a new cluster. !!! Note - If the air-gapped server does not already have TPA installed, follow the instructions [here](../INSTALL/#installing-tpa-without-internet-or-network-access-air-gapped) @@ -88,6 +87,5 @@ would normally. You can use the [upgrade](../tpaexec-upgrade/) command to perform updates in an air-gapped environment. Prior to running this -command you must run `download-packages` on the connected controller, -copy the updated repository to the disconnected controller *and* then -run `deploy` to copy these packages to the target instances. +command you must run `download-packages` on the connected controller and +copy the updated repository to the disconnected controller. diff --git a/product_docs/docs/tpa/23/reference/git-credentials.mdx b/product_docs/docs/tpa/23/reference/git-credentials.mdx index d34d6245f7e..77eb22e2afb 100644 --- a/product_docs/docs/tpa/23/reference/git-credentials.mdx +++ b/product_docs/docs/tpa/23/reference/git-credentials.mdx @@ -24,7 +24,6 @@ disk on the target instance: before running `tpaexec deploy`. !!! Note - When deploying to Docker on macOS, you should use only `https://` repository URLs because Docker containers cannot be accessed by ssh from the host in this environment. diff --git a/product_docs/docs/tpa/23/reference/local-repo.mdx b/product_docs/docs/tpa/23/reference/local-repo.mdx index 2058b499b20..80510daaba2 100644 --- a/product_docs/docs/tpa/23/reference/local-repo.mdx +++ b/product_docs/docs/tpa/23/reference/local-repo.mdx @@ -17,7 +17,6 @@ You can create a local repository manually, or have TPA create one for you. Instructions for both are included below. !!! Note - Specific instructions are available for [managing clusters in an air-gapped](air-gapped/) environment. @@ -93,13 +92,11 @@ the appropriate directory. Then generate metadata using the correct tool for your system as detailed below. !!! Note - You must generate the metadata on the control node, i.e., the machine where you run tpaexec. TPA will copy the metadata and packages to target instances. !!! Note - You must generate the metadata in the subdirectory that the instance will use, i.e., if you copy packages into `local-repo/Debian/10`, you must create the metadata in that directory, not in `local-repo/Debian`. diff --git a/product_docs/docs/tpa/23/tpaexec-upgrade.mdx b/product_docs/docs/tpa/23/tpaexec-upgrade.mdx index 7d2697fd1e9..88e82e79292 100644 --- a/product_docs/docs/tpa/23/tpaexec-upgrade.mdx +++ b/product_docs/docs/tpa/23/tpaexec-upgrade.mdx @@ -67,7 +67,7 @@ unrelated pending changes before you begin the software upgrade process. ## Upgrading from BDR-Always-ON to PGD-Always-ON -To upgrade from BDR-Always-ON to PGD-Always-ON (that is, from BDR4 to +To upgrade from BDR-Always-ON to PGD-Always-ON (that is, from BDR3/4 to PGD5), first run `tpaexec reconfigure`: ``` From 9af920541b9ba372a0c9b6b1238c788924710c5e Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 15 Nov 2023 10:58:32 +0000 Subject: [PATCH 16/19] Fixes (final) Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/INSTALL.mdx | 2 +- product_docs/docs/tpa/23/tpaexec-upgrade.mdx | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/tpa/23/INSTALL.mdx b/product_docs/docs/tpa/23/INSTALL.mdx index bef60e6745a..624376e7c64 100644 --- a/product_docs/docs/tpa/23/INSTALL.mdx +++ b/product_docs/docs/tpa/23/INSTALL.mdx @@ -15,7 +15,7 @@ install TPA from source, please refer to See [Distribution support](reference/distributions/) for information on what platforms are supported. -!!! Important +!!! Info Please make absolutely sure that your system has the correct date and time set, because various things will fail otherwise. We recommend you use a network time, for example `sudo ntpdate diff --git a/product_docs/docs/tpa/23/tpaexec-upgrade.mdx b/product_docs/docs/tpa/23/tpaexec-upgrade.mdx index 88e82e79292..9a21b8a111d 100644 --- a/product_docs/docs/tpa/23/tpaexec-upgrade.mdx +++ b/product_docs/docs/tpa/23/tpaexec-upgrade.mdx @@ -67,6 +67,10 @@ unrelated pending changes before you begin the software upgrade process. ## Upgrading from BDR-Always-ON to PGD-Always-ON +**Note:** The upgrade procedure from BDR-Always-ON to PGD-Always-ON for +camo enabled clusters using BDR version 3.7 is not yet supported. This +support will come in a later release. + To upgrade from BDR-Always-ON to PGD-Always-ON (that is, from BDR3/4 to PGD5), first run `tpaexec reconfigure`: From 774819bb61a4385c3405bfe03c8e08d1c0f45b58 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 15 Nov 2023 11:14:25 +0000 Subject: [PATCH 17/19] Late page (reconciling) Signed-off-by: Dj Walker-Morgan --- .../reference/reconciling-local-changes.mdx | 261 ++++++++++++++++++ 1 file changed, 261 insertions(+) create mode 100644 product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx diff --git a/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx b/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx new file mode 100644 index 00000000000..73c9b6a63ea --- /dev/null +++ b/product_docs/docs/tpa/23/reference/reconciling-local-changes.mdx @@ -0,0 +1,261 @@ +--- +title: Reconciling changes made outside of TPA +originalFilePath: reconciling-local-changes.md + +--- + +Any changes made to a TPA created cluster that are not performed by +changing the TPA configuration will not be saved in `config.yml`. This +means that your cluster will have changes that the TPA configuration +won't be able to recreate. + +This page shows how configuration is managed with TPA and the preferred +ways to make configuration changes. We then look at strategies to make, +and reconcile, the results of making manual changes to the cluster. + +## Why might I need to make manual configuration changes? + +The most common scenario in which you may need to make configuration +changes outside of TPA is if the operation you are performing is not +supported by TPA. The two most common such operations are destructive +changes, such as removing a node, and upgrading the major version of +Postgres. + +### Destructive changes + +In general TPA will not remove previously deployed elements of a +cluster, even if these are removed from `config.yml`. This sometimes +surprises people because a strictly declarative system should always +mutate the deployed artifacts to match the declaration. However, making +destructive changes to production database can have serious consequences +so it is something we have chosen not to support. + +### Major-version Postgres upgrades + +TPA does not yet provide an automated mechanism for performing major +version upgrades of Postgres. Therefore if you need to perform an +in-place upgrade on an existing cluster this must be performed using +other tools such as pg_upgrade or [bdr_pg_upgrade](https://www.enterprisedb.com/docs/pgd/latest/upgrades/bdr_pg_upgrade/#bdr_pg_upgrade-command-line). + +## What can happen if changes are not reconciled? + +A general issue with unreconciled changes is that if you deploy a new +cluster using your existing `config.yml`, or provide your `config.yml` to +EDB Support in order to reproduce a problem, it will not match the +original cluster. In addition, there is potential for operational +problems should you wish to use TPA to manage that cluster in future. + +The operational impact of unreconciled changes varies depending on the +nature of the changes. In particular whether the change is destructive, +and whether the change blocks TPA from running by causing an error or +invalidating the data in `config.yml`. + +### Non-destructive, non-blocking changes + +Additive changes are often accommodated with no immediate operational +issues. Consider manually adding a user. The new user will continue to +exist and cause no issues with TPA at all. You may prefer to manage the +user through TPA in which case you can declare it in `config.yml` but +the existence of a manually-added user will cause no operational issues. + +Some manual additions can have more nuanced effects. Take the example of +an extension which has been manually added. Because TPA does not make +destructive changes, the extension will not be removed when `tpaexec +deploy` is next run. **However**, if you made any changes to the +Postgres configuration to accommodate the new extension these may be +overwritten if you did not make them using one of TPA's supported +mechanisms (see below). + +Furthermore, TPA will not make any attempt to modify the `config.yml` +file to reflect manual changes and the new extension will be omitted +from `tpaexec upgrade` which could lead to incompatible software +versions existing on the cluster. + +### Destructive, non-blocking changes + +Destructive changes that are easily detected and do not block TPA's +operation will simply be undone when `tpaexec deploy` is next run. +Consider manually removing an extension. From the perspective of TPA, +this situation is indistinguishable from the user adding an extension to +the `config.yml` file and running deploy. As such, TPA will add the +extension such that the cluster and the `config.yml` are reconciled, +albeit in the opposite way to that the user intended. + +Similarly, changes made manually to configuration parameters will be +undone unless they are: + +1. Made in the `conf.d/9999-override.conf` file reserved for manual + edits; +2. Made using `ALTER SYSTEM` SQL; or +3. Made [natively in TPA](#postgres_conf_settings) by adding + `postgres_conf_settings`. + +Other than the fact that option 3 is self-documenting and portable, +there is no pressing operational reason to reconcile changes made by +method 1 or 2. + +### Destructive, blocking changes + +Changes which create a more fundamental mismatch between `config.yml` +can block TPA from performing operations. For example if you physically +remove a node in a bare metal cluster, attempts by TPA to connect to +that node will fail, meaning most TPA operations will exit with an error +and you will be unable to manage the cluster with TPA until you +reconcile this difference. + +## How to reconcile configuration changes + +In general, the reconciliation process involves modifying `config.yml` +such that it describes the current state of the cluster and then running +`tpaexec deploy`. + +### Example: parting a PGD node + +Deploy a minimal PGD cluster using the bare architecture and a configure +command such as: + +```bash +tpaexec configure mycluster \ +-a PGD-Always-ON \ +--platform bare \ +--edbpge 15 \ +--location-names a \ +--pgd-proxy-routing local +``` + +Part a node using this SQL, which can be executed from any node: + + select \* from bdr.part_node('node-2'); + +Rerun `deploy`. Note that, whilst no errors occur, the node is still +parted. This can be verified using the command `pgd show-nodes` on any +of the nodes. This is because TPA will not overwrite the metadata which +tells PGD the node is parted. + +!!!Note +It is not possible to reconcile the `config.yml` with this cluster state +because TPA, and indeed PGD itself, has no mechanism to initiate a node +in the 'parted' state. In principle you could continue to use TPA to +continue this parted cluster, but this is not advisable. In most cases +you will wish to continue to fully remove the node and reconcile +`config.yaml`. +!!! + +### Example: removing a PGD node completely + +The previous example parted a node from the PGD cluster, but left the +node itself intact and still managed by TPA in a viable but +unreconcilable state. + +To completely decommission the node, it is safe to simply turn off the +server corresponding to `node-2`. If you attempt to run `deploy` at this +stage, it will fail early when it cannot reach the server. + +To reconcile this change in `config.yml` simply delete the entry under +`instances` corresponding to `node-2`. It will look something like this: + +```yaml +- Name: node-2 + public_ip: 44.201.93.236 + private_ip: 172.31.71.186 + location: a + node: 2 + role: + - bdr + - pgd-proxy + vars: + bdr_child_group: a_subgroup + bdr_node_options: + route_priority: 100 +``` + +You can now manage this node as usual using TPA. However, the original +cluster still has metadata that refers to `node-2` so to complete +reconciliation it is recommended to run the following SQL on each node +to remove the metadata. *This step is essential if you wish to add a +node of the same name in future.* + +```sql +select * from bdr.drop_node('node-2'); +``` + +!!!Note +If you wish to join the original `node-2` back to the cluster after +removing it in this way, you can do so simply by restoring the deleted +lines of `config.yml` but you must ensure that `select * from +bdr.drop_node('node-2');` has been run on this node and that the PGDATA +directory has been deleted. +!!! + +### Example: changing the superuser password + +TPA automatically generates a password for the superuser which you may +view using `tpaexec show-password `. If you +change the password manually (for example using the `/password` command +in psql) you will find that after `tpaexec deploy` is next run, the +password has reverted to the one set by TPA. To make the change through +TPA, and therefore make it persist across runs of `tpaexec deploy`, you +must use the command `tpaexec store-password ` +to specify the password, then run `tpaexec deploy`. This also applies to +any other user created through TPA. + +### Example: adding or removing an extension + +A simple single-node cluster can be deployed with the following +`config.yml`. + +```yaml +--- +architecture: M1 +cluster_name: singlenode + +cluster_vars: + postgres_flavour: postgresql + postgres_version: '15' + preferred_python_version: python3 + tpa_2q_repositories: [] + +instance_defaults: + image: tpa/debian:11 + platform: docker + vars: + ansible_user: root + +instances: +- Name: nodeone + node: 1 + role: + - primary +``` + +You may manually add the pgvector extension by connecting to the node +and running `apt install postgresql-15-pgvector` then executing the +following SQL command: `CREATE EXTENSION vector;`. This will not cause +any operational issues, beyond the fact that `config.yml` no longer +describes the cluster as fully as it did previously. However, it is +advisable to reconcile `config.yml` (or indeed simply use TPA to add the +extension in the first place) by adding the following cluster variables. + +```yaml +cluster_vars: + ... + extra_postgres_packages: + common: + - postgresql-15-pgvector + postgres_extensions: + - vector +``` + +After adding this configuration, you may manually remove the extension +by executing the SQL command `DROP EXTENSION vector;` and then +`apt remove postgresql-15-pgvector`. However if you run `tpaexec deploy` +again without reconciling `config.yml`, the extension will be +reinstalled. To reconcile `config.yml`, simply remove the lines added +previously. + +!!!Note +As noted previously, TPA will not honour destructive changes. +So simply removing the lines from `config.yml` will not remove the +extension. It is necessary to perform this operation manually then +reconcile the change. +!!! From 9215ad53b98c12ca9d15d8f30b5fa81786aa43c1 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 15 Nov 2023 11:34:46 +0000 Subject: [PATCH 18/19] Move reconciling into index Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/reference/index.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/tpa/23/reference/index.mdx b/product_docs/docs/tpa/23/reference/index.mdx index be23517c561..0ad22c1d385 100644 --- a/product_docs/docs/tpa/23/reference/index.mdx +++ b/product_docs/docs/tpa/23/reference/index.mdx @@ -9,6 +9,7 @@ navigation: - Requirements - distributions - tpaexec-support + - reconciling-local-changes - '#Services' - bdr - barman From fbd6d24f1e71711d54e05db6781c005be443d765 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 15 Nov 2023 11:41:18 +0000 Subject: [PATCH 19/19] Reorder index Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/reference/index.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/tpa/23/reference/index.mdx b/product_docs/docs/tpa/23/reference/index.mdx index 0ad22c1d385..3a5ea26939a 100644 --- a/product_docs/docs/tpa/23/reference/index.mdx +++ b/product_docs/docs/tpa/23/reference/index.mdx @@ -9,6 +9,7 @@ navigation: - Requirements - distributions - tpaexec-support + - '#Administration' - reconciling-local-changes - '#Services' - bdr