Merge pull request #5413 from EnterpriseDB/release-2024-03-20a

Release 2024-03-20a
EnterpriseDB · Mar 20, 2024 · 9c0ac9a · 9c0ac9a · github-actions · Mar 20, 2024
2 parents b2fda14 + 0b0f4d7
commit 9c0ac9a
Show file tree

Hide file tree

Showing 11 changed files with 90 additions and 318 deletions.
diff --git a/advocacy_docs/pg_extensions/extensionrefs.json b/advocacy_docs/pg_extensions/extensionrefs.json
@@ -89,6 +89,7 @@
     "autocluster": "https://www.enterprisedb.com/docs/pg_extensions/advanced_storage_pack/",
     "bdr_3.x": "https://www.enterprisedb.com/docs/pgd/3.7/bdr/",
     "bdr_4.x": "https://www.enterprisedb.com/docs/pgd/4/bdr/",
+    "edb_job_scheduler": "https://www.enterprisedb.com/docs/pg_extensions/edb_job_scheduler/",
     "dbms_job": "https://www.enterprisedb.com/docs/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/",
     "dbms_scheduler": "https://www.enterprisedb.com/docs/epas/latest/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/",
     "edb_cloneschema": "https://www.enterprisedb.com/docs/epas/latest/database_administration/14_edb_clone_schema/",
@@ -99,6 +100,7 @@
     "edb_query_advisor": "https://www.enterprisedb.com/docs/pg_extensions/query_advisor/",
     "edb_wait_states": "https://www.enterprisedb.com/docs/pg_extensions/wait_states/",
     "edbspl": "https://www.enterprisedb.com/docs/epas/latest/application_programming/epas_compat_spl/02_spl_programs/",
+    "spl_check": "https://www.enterprisedb.com/docs/pg_extensions/spl_check/",
     "parallel_clone": "undefined",
     "pglogical_3.x": "https://www.enterprisedb.com/docs/pgd/3.7/pglogical/",
     "refdata": "https://www.enterprisedb.com/docs/pg_extensions/advanced_storage_pack/",

diff --git a/advocacy_docs/pg_extensions/index.mdx b/advocacy_docs/pg_extensions/index.mdx
diff --git a/product_docs/docs/biganimal/release/index.mdx b/product_docs/docs/biganimal/release/index.mdx
@@ -9,6 +9,7 @@ directoryDefaults:
 
 navigation:
   - release_notes
+  - known_issues
   - free_trial
   - overview
   - planning

diff --git a/product_docs/docs/biganimal/release/known_issues/index.mdx b/product_docs/docs/biganimal/release/known_issues/index.mdx
@@ -0,0 +1,8 @@
+---
+title: Known Issues and Limitations
+navTitle: Known Issues
+---
+
+This section lists known issues and/or limitations in the current release of BigAnimal and the Postgres deployments it supports:
+
+* [Known Issues with Distributed High Availability](known_issues_dha)
diff --git a/product_docs/docs/biganimal/release/known_issues/known_issues_dha.mdx b/product_docs/docs/biganimal/release/known_issues/known_issues_dha.mdx
@@ -0,0 +1,54 @@
+---
+title: Known Issues with Distributed High Availability/PGD
+navTitle: Distributed High Availability/PGD Known Issues
+deepToC: true
+---
+
+These are currently known issues in EDB Postgres Distributed (PGD) on BigAnimal as deployed in Distributed High Availability clusters. These known issues are tracked in our ticketing system and are expected to be resolved in a future release. 
+
+## Management/Administration
+
+### Deleting a PGD Data Group may not fully reconcile 
+When deleting a PGD Data Group, the target group resources will be physically deleted, but in some cases we have observed that the PGD nodes may not be completely partitioned from the remaining PGD Groups.  It’s recommended to avoid use of this feature until this is fixed and removed from the known issues list. 
+
+### Adjusting PGD cluster architecture may not fully reconcile
+In rare cases, we have observed that changing the node architecture of an existing PGD cluster may not complete. If a change has not taken effect in 1 hour, reach out to Support. 
+
+### PGD Cluster may fail to create due to Azure SKU issue
+In some cases, although a regional quota check may have passed initially when the PGD cluster is created, it may fail if an SKU critical for the Witness Nodes is unavailable across three availability zones.
+To check for this issue at the time of a region quota check, run: 
+
+```
+biganimal-csp-preflight --onboard -i d2s_v3 -x eha <azure-sub-id> <azure-region>
+```
+
+If you have already encountered this issue, reach out to Azure support: 
+
+```plaintext
+We're going to be provisioning a number of instances of <SKU TYPE> in <TARGET REGION> and need to be able to provision these instances in all AZs, can you please ensure that subscription <AA BYOA AZURE SUBSCRIPTION> is able to provision this VM type in all AZs of <TARGET REGION>.  Thank you!
+```
+
+## Replication
+
+### A PGD replication slot may fail to transition cleanly from disconnect to catch up 
+As part of fault injection testing with PGD on BigAnimal, you may decide to delete VMs. Your cluster will recover if you do so, as expected. However, if you are testing in a Bring Your Own Account (BYOA) deployment, in some cases, as the cluster is recovering, a replication slot may remain disconnected. This will persist for a few hours until the replication slot recovers automatically.  
+
+### Replication speed is slow during a large data migration
+During a large data migration, when migrating to a PGD cluster, you may experience a replication rate of 20 MBps. 
+
+### PGD leadership change on healthy cluster
+PGD clusters that are in a healthy state may experience a change in PGD node leadership, potentially resulting in failover. No intervention is needed as a new leader will be appointed.  
+
+## Migration
+
+### Connection interruption disrupts migration via Migration Toolkit 
+When using Migration Toolkit (MTK), if the session is interrupted, the migration will error out. To resolve, you will need to restart the migration from the beginning. The recommended path to avoid this is to migrate on a per-table basis when using MTK so that if this issue does occur, you retry the migration with a table rather than the whole database.  
+
+### Ensure loaderCount is less than 1 in Migration ToolKit 
+When using Migration Toolkit to migrate a PGD cluster, if you have adjusted the loaderCount to be greater than 1 in order to speed up migration, you may see an error in the MTK CLI that says “pgsql_tmp/': No such file or directory.” If you see this, reduce your loaderCount to 1 in MTK. 
+
+## Tools
+
+### Verify-settings command via PGD CLI provides false negative for PGD on BigAnimal clusters
+The command verify-settings in the PGD CLI will display that a “node is unreachable” when used with PGD on BigAnimal clusters. 
+
diff --git 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.31_rel_notes
  - tpa_23.30_rel_notes
  - tpa_23.29_rel_notes
  - tpa_23.28_rel_notes
@@ -28,6 +29,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru
 
 |           Version            | Release date |
 | ---------------------------- | ------------ |
+| [23.31](tpa_23.31_rel_notes) | 19 Mar 2024  |
 | [23.30](tpa_23.30_rel_notes) | 19 Mar 2024  |
 | [23.29](tpa_23.29_rel_notes) | 15 Feb 2024  |
 | [23.28](tpa_23.28_rel_notes) | 23 Jan 2024  |

diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.31_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.31_rel_notes.mdx
@@ -0,0 +1,12 @@
+---
+title: Trusted Postgres Architect 23.31 release notes 
+navTitle: "Version 23.31"
+---
+
+Released: 19 Mar 2024
+
+New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.31 include the following:
+
+| Type | Description |
+| ---- |------------ |
+| Bug Fix | Fixed a critical bug whereby deployments could fail due to a syntax error.|