Merge pull request #5196 from EnterpriseDB/release/2024-29-01a

Release/2024-29-01a
EnterpriseDB · Jan 29, 2024 · f1af82b · f1af82b · github-actions · Jan 29, 2024
2 parents f87080d + dc96738
commit f1af82b
Show file tree

Hide file tree

Showing 12 changed files with 124 additions and 104 deletions.
diff --git a/product_docs/docs/biganimal/release/getting_started/managing_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/managing_cluster.mdx
@@ -22,7 +22,7 @@ After seven days, single-node and high-availability clusters automatically resum
 2.  Do one of the following:
     -   In the row for the cluster, at right, from the ellipsis menu, select **Pause Cluster**.
     -   Select the cluster you want to pause. From **Quick Actions** on the cluster details page, select **Pause Cluster**.
-3.  Confirm that you want to pause the cluster. When the process finishes, the cluster status appears as Paused.
+3.  Confirm that you want to pause the cluster. When the process finishes, the cluster status appears as Paused. It may take up to 15 minutes for the compute instance in your CSP to scale down.
 
 ### Resuming a cluster
 

diff --git a/...4_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx b/...4_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx
@@ -22,7 +22,7 @@ The target cluster must not contain any data; you can create an empty cluster us
 
 The easiest way to empty the target database is to drop the database and then create a new database. Before invoking the `DROP DATABASE` command, you must disconnect any users and halt any services that are currently using the database.
 
-On Windows, navigate through the `Control Panel` to the `Services` manager; highlight each service in the `Services` list, and select `Stop`.
+On Windows, navigate through the `Control Panel` to the `Services` manager, highlight each service in the `Services` list, and select `Stop`.
 
 On Linux, open a terminal window, assume superuser privileges, and manually stop each service; for example, invoke the following command to stop the pgAgent service:
 
@@ -48,7 +48,7 @@ CREATE DATABASE <database_name>;
 
 During the upgrade process, `pg_upgrade` connects to the old and new servers several times; to make the connection process easier, you can edit the `pg_hba.conf` file, setting the authentication mode to `trust`. To modify the `pg_hba.conf` file, navigate through the `Start` menu to the `EDB Postgres` menu; to the `EDB Postgres Advanced Server` menu, and open the `Expert Configuration` menu; select the `Edit pg_hba.conf` menu option to open the `pg_hba.conf` file.
 
-You must allow trust authentication for the previous EDB Postgres Advanced Server installation, and EDB Postgres Advanced Server 14 servers. Edit the `pg_hba.conf` file for both installations of EDB Postgres Advanced Server as shown in the following figure.
+You must allow trust authentication for the previous EDB Postgres Advanced Server installation and EDB Postgres Advanced Server 14 servers. Edit the `pg_hba.conf` file for both installations of EDB Postgres Advanced Server as shown in the following figure.
 
 ![Configuring EDB Postgres Advanced Server to use trust authentication.](../images/configuring_advanced_server_to_use_trust_authentication.png)
 
@@ -69,13 +69,13 @@ The services that are most likely to be running in your installation are:
 
 | Service                                        | On Linux                               | On Windows                                                 |
 | ---------------------------------------------- | -------------------------------------- | ---------------------------------------------------------- |
-| EnterprisEDB Postgres Advanced Server 9.6      | edb-as-9.6                             | edb-as-9.6                                                 |
-| EnterprisEDB Postgres Advanced Server 10       | edb-as-10                              | edb-as-10                                                  |
-| EnterprisEDB Postgres Advanced Server 11       | edb-as-11                              | edb-as-11                                                  |
-| EnterprisEDB Postgres Advanced Server 12       | edb-as-12                              | edb-as-12                                                  |
-| EnterprisEDB Postgres Advanced Server 13       | edb-as-13                              | edb-as-13                                                  |
-| EnterprisEDB Postgres Advanced Server 14       | edb-as-14                              | edb-as-14                                                  |
-| EDB Postgres Advanced Server 9.6 Scheduling Agent (pgAgent) | edb-pgagent-9.6                        | EnterprisEDB Postgres Advanced Server 9.6 Scheduling Agent |
+| EDB Postgres Advanced Server 9.6      | edb-as-9.6                             | edb-as-9.6                                                 |
+| EDB Postgres Advanced Server 10       | edb-as-10                              | edb-as-10                                                  |
+| EDB Postgres Advanced Server 11       | edb-as-11                              | edb-as-11                                                  |
+| EDB Postgres Advanced Server 12       | edb-as-12                              | edb-as-12                                                  |
+| EDB Postgres Advanced Server 13       | edb-as-13                              | edb-as-13                                                  |
+| EDB Postgres Advanced Server 14       | edb-as-14                              | edb-as-14                                                  |
+| EDB Postgres Advanced Server 9.6 Scheduling Agent (pgAgent) | edb-pgagent-9.6                        | EDB Postgres Advanced Server 9.6 Scheduling Agent |
 | Infinite Cache 9.6                             | edb-icache                             | N/A                                                        |
 | Infinite Cache 10                              | edb-icache                             | N/A                                                        |
 | PgBouncer                                      | Pgbouncer                              | Pgbouncer                                                  |
@@ -151,7 +151,7 @@ The `PsExec` program must be obtained by downloading `PsTools`, which is availab
 
 <https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx>.
 
-You can then use the following command to run `CMD.EXE` as `NT AUTHORITY\NetworkService`, and then set the path to the `pg_upgrade` executable.
+You can then use the following command to run `CMD.EXE` as `NT AUTHORITY\NetworkService` and then set the path to the `pg_upgrade` executable.
 
 ```text
 psexec.exe -u "NT AUTHORITY\NetworkService" CMD.EXE

diff --git a/product_docs/docs/epas/15/epas_security_guide/tde_feature.mdx b/product_docs/docs/epas/15/epas_security_guide/tde_feature.mdx
@@ -5,7 +5,7 @@ description: "Provides an overview of the benefits of the Transparent Data Encry
 
 Transparent Data Encryption (TDE) is an optional encryption method that protects data in the database by encrypting the underlying files.
 
-TDE is transparent to authorized users of the database, as no change is required in the applications or existing access policies. It's supported by version 15 of EDB Postgres Advanced Server and EDB Postgres Extended Server with high availability.
+TDE is transparent to authorized users of the database, as no change is required in the applications or existing access policies. It's supported by EDB Postgres Advanced Server and EDB Postgres Extended Server, in versions 15 and above, with high availability.
 
 TDE hardens your organization’s data security with minimum performance overhead and doesn't require additional storage. TDE also enables developers to secure their data using secure encryption algorithms without changing their applications. The feature securely stores individual tablespaces and logs encrypted with their own encryption keys, ensuring security of user data while preserving ease of management for database administrators.
 

diff --git a/...4_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx b/...4_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server.mdx
@@ -53,7 +53,7 @@ You must allow trust authentication for the previous EDB Postgres Advanced Serve
 
 ![Configuring EDB Postgres Advanced Server to use trust authentication.](../../images/configuring_advanced_server_to_use_trust_authentication.png)
 
-After editing each file, save the file, and exit the editor.
+After editing each file, save the file and exit the editor.
 
 If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/libpq-pgpass.html).
 
@@ -66,14 +66,14 @@ The services in the table are most likely to be running in your installation.
 
 | Service                                        | On Linux                               | On Windows                                                 |
 | ---------------------------------------------- | -------------------------------------- | ---------------------------------------------------------- |
-| EnterprisEDB Postgres Advanced Server 9.6      | edb-as-9.6                             | edb-as-9.6                                                 |
-| EnterprisEDB Postgres Advanced Server 10       | edb-as-10                              | edb-as-10                                                  |
-| EnterprisEDB Postgres Advanced Server 11       | edb-as-11                              | edb-as-11                                                  |
-| EnterprisEDB Postgres Advanced Server 12       | edb-as-12                              | edb-as-12                                                  |
-| EnterprisEDB Postgres Advanced Server 13       | edb-as-13                              | edb-as-13                                                  |
-| EnterprisEDB Postgres Advanced Server 14       | edb-as-14                              | edb-as-14                                                  |
-| EnterprisEDB Postgres Advanced Server 15       | edb-as-15                              | edb-as-15                                                  |
-| EDB Postgres Advanced Server 9.6 Scheduling Agent (pgAgent) | edb-pgagent-9.6                        | EnterprisEDB Postgres Advanced Server 9.6 Scheduling Agent |
+| EDB Postgres Advanced Server 9.6      | edb-as-9.6                             | edb-as-9.6                                                 |
+| EDB Postgres Advanced Server 10       | edb-as-10                              | edb-as-10                                                  |
+| EDB Postgres Advanced Server 11       | edb-as-11                              | edb-as-11                                                  |
+| EDB Postgres Advanced Server 12       | edb-as-12                              | edb-as-12                                                  |
+| EDB Postgres Advanced Server 13       | edb-as-13                              | edb-as-13                                                  |
+| EDB Postgres Advanced Server 14       | edb-as-14                              | edb-as-14                                                  |
+| EDB Postgres Advanced Server 15       | edb-as-15                              | edb-as-15                                                  |
+| EDB Postgres Advanced Server 9.6 Scheduling Agent (pgAgent) | edb-pgagent-9.6                        | EDB Postgres Advanced Server 9.6 Scheduling Agent |
 | Infinite Cache 9.6                             | edb-icache                             | N/A                                                        |
 | Infinite Cache 10                              | edb-icache                             | N/A                                                        |
 | PgBouncer                                      | Pgbouncer                              | Pgbouncer                                                  |
@@ -109,7 +109,7 @@ su - enterprisedb
 If prompted, enter the EDB Postgres Advanced Server cluster owner password. Then, set the path to include the location of the `pg_upgrade` executable:
 
 ```shell
-export PATH=$PATH:/usr/edb/as14/bin
+export PATH=$PATH:/usr/edb/as15/bin
 ```
 
 During the upgrade process, `pg_upgrade` writes a file to the current working directory of the `enterprisedb` user. You must invoke `pg_upgrade` from a directory where the `enterprisedb` user has write privileges. After performing the previous commands, navigate to a directory in which the `enterprisedb` user has sufficient privileges to write a file.
@@ -126,7 +126,7 @@ If the `--serviceaccount service_account_user` parameter was specified during th
 
 ```sql
 RUNAS /USER:service_account_user "CMD.EXE"
-SET PATH=%PATH%;C:\Program Files\edb\as14\bin
+SET PATH=%PATH%;C:\Program Files\edb\as15\bin
 ```
 
 During the upgrade process, `pg_upgrade` writes a file to the current working directory of the service account user. You must invoke `pg_upgrade` from a directory where the service account user has write privileges. After performing the previous commands, navigate to a directory in which the service account user has privileges to write a file:
@@ -147,7 +147,7 @@ You can then use the following command to run `CMD.EXE` as `NT AUTHORITY\Network
 
 ```shell
 psexec.exe -u "NT AUTHORITY\NetworkService" CMD.EXE
-SET PATH=%PATH%;C:\Program Files\edb\as14\bin
+SET PATH=%PATH%;C:\Program Files\edb\as15\bin
 ```
 
 During the upgrade process, `pg_upgrade` writes a file to the current working directory of the service account user. You must invoke `pg_upgrade` from a directory where the service account user has write privileges. After performing the previous commands, navigate to a directory in which the service account user has privileges to write a file:
@@ -163,9 +163,9 @@ Before attempting an upgrade, perform a consistency check to ensure that the old
 This example shows invoking `pg_upgrade` to perform a consistency check on Linux:
 
 ```shell
-pg_upgrade -d /var/lib/edb/as13/data
--D /var/lib/edb/as14/data -U enterprisedb
--b /usr/edb/as13/bin -B /usr/edb/as14/bin -p 5444 -P 5445 --check
+pg_upgrade -d /var/lib/edb/as14/data
+-D /var/lib/edb/as15/data -U enterprisedb
+-b /usr/edb/as14/bin -B /usr/edb/as15/bin -p 5444 -P 5445 --check
 ```
 
 If the command is successful, it returns `*Clusters are compatible*`.
@@ -174,10 +174,10 @@ If you're using Windows, quote any directory names that contain a space:
 
 ```shell
 pg_upgrade.exe
--d "C:\Program Files\ PostgresPlus\13AS\data"
--D "C:\Program Files\edb\as14\data" -U enterprisedb
--b "C:\Program Files\PostgresPlus\13AS\bin"
--B "C:\Program Files\edb\as14\bin" -p 5444 -P 5445 --check
+-d "C:\Program Files\ PostgresPlus\14AS\data"
+-D "C:\Program Files\edb\as15\data" -U enterprisedb
+-b "C:\Program Files\PostgresPlus\14AS\bin"
+-B "C:\Program Files\edb\as15\bin" -p 5444 -P 5445 --check
 ```
 
 During the consistency checking process, `pg_upgrade` logs any discrepancies that it finds to a file located in the directory from which you invoked `pg_upgrade`. When the consistency check completes, review the file to identify any missing components or upgrade conflicts. Resolve any conflicts before invoking `pg_upgrade` to perform a version upgrade.
@@ -193,25 +193,25 @@ After confirming that the clusters are compatible, you can invoke `pg_upgrade` t
 On Linux:
 
 ```shell
-pg_upgrade -d /var/lib/edb/as13/data
--D /var/lib/edb/as14/data -U enterprisedb
--b /usr/edb/as13/bin -B /usr/edb/as14/bin -p 5444 -P 5445
+pg_upgrade -d /var/lib/edb/as14/data
+-D /var/lib/edb/as15/data -U enterprisedb
+-b /usr/edb/as14/bin -B /usr/edb/as15/bin -p 5444 -P 5445
 ```
 
 On Windows:
 
 ```shell
-pg_upgrade.exe -d "C:\Program Files\PostgresPlus\13AS\data"
--D "C:\Program Files\edb\as14\data" -U enterprisedb
--b "C:\Program Files\PostgresPlus\13AS\bin"
--B "C:\Program Files\edb\as14\bin" -p 5444 -P 5445
+pg_upgrade.exe -d "C:\Program Files\PostgresPlus\14AS\data"
+-D "C:\Program Files\edb\as15\data" -U enterprisedb
+-b "C:\Program Files\PostgresPlus\14AS\bin"
+-B "C:\Program Files\edb\as15\bin" -p 5444 -P 5445
 ```
 
 `pg_upgrade` displays the progress of the upgrade onscreen:
 
 ```shell
-$ pg_upgrade -d /var/lib/edb/as13/data -D /var/lib/edb/as14/data -U
-enterprisedb -b /usr/edb/as13/bin -B /usr/edb/as14/bin -p 5444 -P 5445
+$ pg_upgrade -d /var/lib/edb/as14/data -D /var/lib/edb/as15/data -U
+enterprisedb -b /usr/edb/as14/bin -B /usr/edb/as15/bin -p 5444 -P 5445
 Performing Consistency Checks
 -----------------------------
 Checking current, bin, and data directories            ok

diff --git a/product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx b/product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx
@@ -5,7 +5,7 @@ description: "Provides an overview of the benefits of the Transparent Data Encry
 
 Transparent Data Encryption (TDE) is an optional encryption method that protects data in the database by encrypting the underlying files.
 
-TDE is transparent to authorized users of the database, as no change is required in the applications or existing access policies. It's supported by version 15 of EDB Postgres Advanced Server and EDB Postgres Extended Server with high availability.
+TDE is transparent to authorized users of the database, as no change is required in the applications or existing access policies. It's supported by EDB Postgres Advanced Server and EDB Postgres Extended Server, in versions 15 and above, with high availability.
 
 TDE hardens your organization’s data security with minimum performance overhead and doesn't require additional storage. TDE also enables developers to secure their data using secure encryption algorithms without changing their applications. The feature securely stores individual tablespaces and logs encrypted with their own encryption keys, ensuring security of user data while preserving ease of management for database administrators.