Merge pull request #4701 from EnterpriseDB/release/2023-08-25

Release: 2023-08-25
EnterpriseDB · Aug 25, 2023 · a53aaa8 · a53aaa8 · github-actions · Aug 25, 2023
2 parents da3cc9d + b03eef9
commit a53aaa8
Show file tree

Hide file tree

Showing 15 changed files with 40 additions and 52 deletions.
diff --git a/product_docs/docs/biganimal/release/overview/updates.mdx b/product_docs/docs/biganimal/release/overview/updates.mdx
@@ -8,7 +8,7 @@ EDB reserves the right to upgrade customers to the latest minor version without
 
 In some cases, these updates might terminate existing network connections to your clusters. If that happens, the outage is typically less than 30 seconds. Be sure your applications are configured to automatically reconnect when connections are interrupted. Most modern database libraries do this by default. 
 
-If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of an extreme-high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). 
+If you want to control when the updates are pushed, you can specify a weekly maintenance window for each cluster or each data group in the case of a distributed high-availability cluster. BigAnimal displays a *scheduled maintenance* message on your cluster list four hours prior to the scheduled maintenance time to remind you of the upcoming maintenance window. This reminder allows you to make any necessary preparations, such as saving your work and closing any open connections. For more information on specifying maintenance windows, see [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). 
 
 
 ## Connectivity issues after an automatic upgrade

diff --git a/...t_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/...t_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx
@@ -25,14 +25,14 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre
 
    |                       Settings                       |         Tab         |                                                                                                                                                                                Notes                                                                                                                                                                                 |
    | ---------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-   | Cluster type                                         | **Cluster Info**        | You can't switch from a single-node cluster or a high-availability cluster to an extreme-high-availability cluster or vice versa.                                                                                                                                                                                                                                    |
+   | Cluster type                                         | **Cluster Info**        | You can't switch from a single-node cluster or a high-availability cluster to a distributed high-availability cluster or vice versa.                                                                                                                                                                                                                                    |
    | Number of replicas (for a high-availability cluster) | **Cluster Info**        | &mdash;                                                                                                                                                                                                                                                                                                                                                                  |
    | Cluster name and password                            | **Cluster Settings**    | &mdash;                                                                                                                                                                                                                                                                                                                                                                   |
    | Instance type                                        | **Cluster Settings**    | Changing the instance type can incur higher cloud infrastructure charges.                                                                                                                                                                                                                                                                                            |
    | Volume type                                          | **Cluster Settings**    | You can't switch between the io2 and io2 Block Express volume types in an AWS cluster.                                                                                                                                                                                                                                                                              |
    | Volume properties                                    | **Cluster Settings**    | It can take up to six hours to tune IOPS or resize the disks of your cluster because AWS requires a cooldown period after volume modifications, as explained in [Limitations](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/modify-volume-requirements.html). The volume properties are disabled and can't be modified while this is in progress. |
    | Networking type (public or private)                  | **Cluster Settings**    | If you're using Azure and previously set up a private link and want to change to a public network, you must remove the private link resources before making the change.                                                                                                                                                                                            |
-   | Nodes (for an extreme-high-availability cluster)     | **Data Groups**         | &mdash;                                                                                                                                                                                                                                                                                                                                                                     |
+   | Nodes (for a distributed high-availability cluster)     | **Data Groups**         | &mdash;                                                                                                                                                                                                                                                                                                                                                                     |
    | Database configuration parameters                    | **DB Configuration**    | If you're using faraway replicas, only a small subset of parameters are editable. These parameters need to be modified in the replica when increased in the replica's source cluster. See [Modify a faraway replica](/biganimal/latest/using_cluster/managing_replicas/#modify-a-faraway-replica) for details.                                                        |
    | Retention period for backups                         | **Additional Settings** | &mdash;                                                                                                                                                                                                                                                                                                                                                                   |
    | Custom maintenance window                            | **Additional Settings** | Set or modify a maintenance window in which maintenance upgrades occur for the cluster. See [Maintenance](/biganimal/latest/getting_started/creating_a_cluster/#maintenance). |
@@ -48,7 +48,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre
 
 ## Modify a data group
 
-You can modify the data groups in your extreme-high-availability cluster by editing the configuration settings.
+You can modify the data groups in your distributed high-availability cluster by editing the configuration settings.
 
 1. Sign in to the [BigAnimal portal](https://portal.biganimal.com).
 

diff --git a/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx b/product_docs/docs/biganimal/release/using_cluster/managing_replicas.mdx
@@ -97,7 +97,7 @@ You can promote a faraway replica to a full-fledged cluster, which makes it capa
 1. The cluster settings are populated with values inherited from the source cluster. You can edit the cluster settings while creating your cluster. 
 
    !!! NoteNotes
-       - You can promote a faraway replica to a single node or high-availability cluster but not to an extreme-high-availability cluster. 
+       - You can promote a faraway replica to a single node or high-availability cluster but not to a distributed high-availability cluster. 
        - While promoting a replica to a cluster, you can't modify the **Provider** and **Region** fields and the **Database Type** section or enable read-only workloads.
 
 1. Select **Promote Replica**. 

diff --git a/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/11/installing/linux_install_details/component_locations.mdx
@@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director
 | --------------------------------- | ------------------------------------------ |
 | Executables                       | `/usr/edb/as11/bin`                        |
 | Libraries                         | `/usr/edb/as11/lib`                        |
-| Cluster configuration files       | `/etc/edb/as11`                            |
+| Cluster configuration files       | `/var/lib/edb/as11`                        |
 | Documentation                     | `/usr/edb/as11/share/doc`                  |
 | Contrib                           | `/usr/edb/as11/share/contrib`              |
 | Data                              | `/var/lib/edb/as11/data`                   |
-| Logs                              | `/var/log/as11`                            |
-| Lock files                        | `/var/lock/as11`                           |
-| Log rotation file                 | `/etc/logrotate.d/as11`                    |
-| Sudo configuration file           | `/etc/sudoers.d/as11`                      |
-| Binary to access VIP without sudo | `/usr/edb/as11/bin/secure`                 |
+| Logs                              | `/var/log/edb/as11`                        |
+| Lock files                        | `/var/lock/edb/as11`                       |
 | Backup area                       | `/var/lib/edb/as11/backups`                |
 | Templates                         | `/usr/edb/as11/share`                      |
 | Procedural Languages              | `/usr/edb/as11/lib or /usr/edb/as11/lib64` |

diff --git a/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/12/installing/linux_install_details/component_locations.mdx
@@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director
 | --------------------------------- | ------------------------------------------ |
 | Executables                       | `/usr/edb/as12/bin`                        |
 | Libraries                         | `/usr/edb/as12/lib`                        |
-| Cluster configuration files       | `/etc/edb/as12`                            |
+| Cluster configuration files       | `/var/lib/edb/as12`                        |
 | Documentation                     | `/usr/edb/as12/share/doc`                  |
 | Contrib                           | `/usr/edb/as12/share/contrib`              |
 | Data                              | `/var/lib/edb/as12/data`                   |
-| Logs                              | `/var/log/as12`                            |
-| Lock files                        | `/var/lock/as12`                           |
-| Log rotation file                 | `/etc/logrotate.d/as12`                    |
-| Sudo configuration file           | `/etc/sudoers.d/as12`                      |
-| Binary to access VIP without sudo | `/usr/edb/as12/bin/secure`                 |
+| Logs                              | `/var/log/edb/as12`                        |
+| Lock files                        | `/var/lock/edb/as12`                       |
 | Backup area                       | `/var/lib/edb/as12/backups`                |
 | Templates                         | `/usr/edb/as12/share`                      |
 | Procedural Languages              | `/usr/edb/as12/lib or /usr/edb/as12/lib64` |

diff --git a/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/13/installing/linux_install_details/component_locations.mdx
@@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director
 | --------------------------------- | ------------------------------------------ |
 | Executables                       | `/usr/edb/as13/bin`                        |
 | Libraries                         | `/usr/edb/as13/lib`                        |
-| Cluster configuration files       | `/etc/edb/as13`                            |
+| Cluster configuration files       | `/var/lib/edb/as13`                        |
 | Documentation                     | `/usr/edb/as13/share/doc`                  |
 | Contrib                           | `/usr/edb/as13/share/contrib`              |
 | Data                              | `/var/lib/edb/as13/data`                   |
-| Logs                              | `/var/log/as13`                            |
-| Lock files                        | `/var/lock/as13`                           |
-| Log rotation file                 | `/etc/logrotate.d/as13`                    |
-| Sudo configuration file           | `/etc/sudoers.d/as13`                      |
-| Binary to access VIP without sudo | `/usr/edb/as13/bin/secure`                 |
+| Logs                              | `/var/log/edb/as13`                        |
+| Lock files                        | `/var/lock/edb/as13`                       |
 | Backup area                       | `/var/lib/edb/as13/backups`                |
 | Templates                         | `/usr/edb/as13/share`                      |
 | Procedural Languages              | `/usr/edb/as13/lib or /usr/edb/as13/lib64` |

diff --git a/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/14/installing/linux_install_details/component_locations.mdx
@@ -17,15 +17,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director
 | --------------------------------- | ------------------------------------------ |
 | Executables                       | `/usr/edb/as14/bin`                        |
 | Libraries                         | `/usr/edb/as14/lib`                        |
-| Cluster configuration files       | `/etc/edb/as14`                            |
+| Cluster configuration files       | `/var/lib/edb/as14`                        |
 | Documentation                     | `/usr/edb/as14/share/doc`                  |
 | Contrib                           | `/usr/edb/as14/share/contrib`              |
 | Data                              | `/var/lib/edb/as14/data`                   |
-| Logs                              | `/var/log/as14`                            |
-| Lock files                        | `/var/lock/as14`                           |
-| Log rotation file                 | `/etc/logrotate.d/as14`                    |
-| Sudo configuration file           | `/etc/sudoers.d/as14`                      |
-| Binary to access VIP without sudo | `/usr/edb/as14/bin/secure`                 |
+| Logs                              | `/var/log/edb/as14`                        |
+| Lock files                        | `/var/lock/edb/as14`                       |
 | Backup area                       | `/var/lib/edb/as14/backups`                |
 | Templates                         | `/usr/edb/as14/share`                      |
 | Procedural Languages              | `/usr/edb/as14/lib or /usr/edb/as14/lib64` |

diff --git a/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/15/installing/linux_install_details/component_locations.mdx
@@ -18,15 +18,12 @@ The RPM installers place EDB Postgres Advanced Server components in the director
 | --------------------------------- | ------------------------------------------ |
 | Executables                       | `/usr/edb/as15/bin`                        |
 | Libraries                         | `/usr/edb/as15/lib`                        |
-| Cluster configuration files       | `/etc/edb/as15`                            |
+| Cluster configuration files       | `/var/lib/edb/as15`                            |
 | Documentation                     | `/usr/edb/as15/share/doc`                  |
 | Contrib                           | `/usr/edb/as15/share/contrib`              |
 | Data                              | `/var/lib/edb/as15/data`                   |
-| Logs                              | `/var/log/as15`                            |
-| Lock files                        | `/var/lock/as15`                           |
-| Log rotation file                 | `/etc/logrotate.d/as15`                    |
-| Sudo configuration file           | `/etc/sudoers.d/as15`                      |
-| Binary to access VIP without sudo | `/usr/edb/as15/bin/secure`                 |
+| Logs                              | `/var/log/edb/as15`                            |
+| Lock files                        | `/var/lock/edb/as15`                           |
 | Backup area                       | `/var/lib/edb/as15/backups`                |
 | Templates                         | `/usr/edb/as15/share`                      |
 | Procedural Languages              | `/usr/edb/as15/lib or /usr/edb/as15/lib64` |

diff --git a/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx b/product_docs/docs/eprs/7/installing/upgrading_replication_server/index.mdx
@@ -15,11 +15,12 @@ It is assumed that you are installing Replication Server 7.x on the same host ma
 If you are using a version of Replication Server earlier than 6.2.x on Linux, first upgrade to 6.2.x, and then upgrade to version 7.x. See:
 - [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package)
 
-
 For more details on upgrading Replication Server, see:
 
 - [Updating the publication and subscription server](updating_sub_and_pub_ports)
 - [Upgrading from a Replication Server 7.x installation on Linux](upgrading_linux)
 - [Upgrading with the graphical user interface installer](upgrading_with_gui_installer)
 
+After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it (for Linux) or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information.
+
 
diff --git a/...ct_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx b/...ct_docs/docs/eprs/7/installing/upgrading_replication_server/upgrading_linux.mdx
@@ -15,3 +15,6 @@ If you have an existing Replication Server 7.x installation on Linux, you can us
 `yum upgrade edb-xdb*`
 
 If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details.
+
+After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information.
+
diff --git a/...eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx b/...eprs/7/installing/upgrading_replication_server/upgrading_with_gui_installer.mdx
@@ -47,6 +47,8 @@ You can upgrade to Replication Server 7 using the graphical user interface insta
 
     If you don't need to adjust the port numbers, register the publication server and subscription server with the Replication Server console as described in [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). The existing replication systems appear in the replication tree of the Replication Server Console.
 
+After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink (for Linux) to it or rename the driver (for Windows). See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information.
+
 You are now ready to use Replication Server 7 to create new replication systems and manage existing ones.
 
 !!! Note
Original file line number	Diff line number	Diff line change
Expand Up		@@ -15,3 +15,6 @@ If you have an existing Replication Server 7.x installation on Linux, you can us
		`yum upgrade edb-xdb*`

		If you are upgrading from a Replication Server 6.2 installation on Linux, see [Upgrading from a Replication Server 6.2 installation on Linux](upgrading_with_xdb_rpm_package) for details.

		After upgrading and before using Replication Server, you need to download a JDBC driver and create a symlink to it. See [Installing a JDBC driver](enterprisedb.com/docs/eprs/latest/installing/installing_jdbc_driver/) for more information.