Merge pull request #4296 from EnterpriseDB/release/2023-06-23

Release: 2023-06-23
EnterpriseDB · Jun 23, 2023 · 0e21044 · 0e21044 · github-actions · Jun 23, 2023
2 parents e252781 + 49f6fc3
commit 0e21044
Show file tree

Hide file tree

Showing 22 changed files with 241 additions and 243 deletions.
diff --git a/product_docs/docs/biganimal/release/using_cluster/01_postgres_access/index.mdx b/product_docs/docs/biganimal/release/using_cluster/01_postgres_access/index.mdx
@@ -23,7 +23,7 @@ psql -W "postgres://[email protected]:5432/edb_admin?sslmod
 ## Admin roles
 
 ### pg_ba_admin
-So that we can effectively manage the cloud resources and ensure users are protected against security threats, BigAnimal provides a special administrative role, pg_ba_admin. The edb_admin user is a member of the pg_ba_admin role. The pg_ba_admin role has privileges similar to a Postgres superuser. Like the edb_admin user, the pg_ba_admin role shouldn't be be used for day-to-day application operations and access to the role must be controlled carefully. See [pg_ba_admin role](pg_ba_admin) for details.
+So that we can effectively manage the cloud resources and ensure users are protected against security threats, BigAnimal provides a special administrative role, pg_ba_admin. The edb_admin user is a member of the pg_ba_admin role. The pg_ba_admin role has privileges similar to a Postgres superuser. Like the edb_admin user, the pg_ba_admin role shouldn't be used for day-to-day application operations and access to the role must be controlled carefully. See [pg_ba_admin role](pg_ba_admin) for details.
 
 The pg_ba_admin role is present on clusters deployed in BigAnimal's cloud account. Soon, it will be deployed to all BigAnimal clusters.
 

diff --git a/...t_docs/docs/epas/15/epas_compat_bip_guide/02_packages/01_package_components.mdx b/...t_docs/docs/epas/15/epas_compat_bip_guide/02_packages/01_package_components.mdx
@@ -9,7 +9,7 @@ legacyRedirectsGenerated:
 Packages consist of two main components:
 
 -   The package specification, which is the public interface. You can reference these elements outside the package. Declare all database objects that are a part of a package in the specification.
--   Th package body, which contains the actual implementation of all the database objects declared in the package specification.
+-   The package body, which contains the actual implementation of all the database objects declared in the package specification.
 
   The package body implements the specifications in the package specification. It contains implementation details and private declarations that are invisible to the application. You can debug, enhance, or replace a package body without changing the specifications. Similarly, you can change the body without recompiling the calling programs because the implementation details are invisible to the application.
 

diff --git a/product_docs/docs/pgd/5/appusage.mdx b/product_docs/docs/pgd/5/appusage.mdx
@@ -182,7 +182,7 @@ See [Release notes](/pgd/latest/rel_notes/) for any known incompatibilities.
 
 ## Replicating between nodes with differences
 
-By default, DDL is automatically sent to all nodes. You can control this manually, as described in [DDL Replication](ddl), and you can use it to create differences between database schemas across nodes.
+By default, DDL is automatically sent to all nodes. You can control this manually, as described in [DDL replication](ddl), and you can use it to create differences between database schemas across nodes.
 PGD is designed to allow replication to continue even with minor
 differences between nodes. These features are designed to allow
 application schema migration without downtime or to allow logical
@@ -326,7 +326,7 @@ its different modes.
 ## Application testing
 
 You can test PGD applications using the following programs,
-in addition to other techniques.
+in addition to other techniques:
 
 -   [Trusted Postgres Architect](#trusted-postgres-architect)
 -   [pgbench with CAMO/Failover options](#pgbench-with-camofailover-options)
@@ -391,7 +391,6 @@ this scenario there's no way to find the status of in-flight transactions.
 
 ### isolationtester with multi-node access
 
-
 `isolationtester` was extended to allow users to run tests on multiple
 sessions and on multiple nodes. This tool is used for internal PGD testing,
 although it's also available for use with user application testing.

diff --git a/product_docs/docs/pgd/5/architectures.mdx b/product_docs/docs/pgd/5/architectures.mdx
@@ -137,7 +137,7 @@ Use these criteria to help you to select the appropriate Always On architecture.
 | Global consensus in case of location failure         | N/A                                                      | No                                                       | Yes                                                      | Yes                                                      |
 | Data restore required after location failure         | Yes                                                      | No                                                       | No                                                       | No                                                       |
 | Immediate failover in case of location failure       | No - requires data restore from backup                   | Yes - alternate Location                                 | Yes - alternate Location                                 | Yes - alternate Location                                 |
-| Cross Location Network Traffic                       | Only if backup is offsite                                | Full replication traffic                                 | Full replication traffic                                 | Full replication traffic                                 |
-| License Cost                                         | 2 or 3 PGD data nodes                                    | 4 or 6  PGD data nodes                                   | 4 or 6 PGD data nodes                                    | 6+ PGD data nodes                                        |
+| Cross-location network traffic                       | Only if backup is offsite                                | Full replication traffic                                 | Full replication traffic                                 | Full replication traffic                                 |
+| License cost                                         | 2 or 3 PGD data nodes                                    | 4 or 6  PGD data nodes                                   | 4 or 6 PGD data nodes                                    | 6+ PGD data nodes                                        |