Merge pull request #3953 from EnterpriseDB/release/2023-04-20

Release: 2023-04-20

advocacy_docs/pg_extensions/pg_failover_slots/installing.mdx

@@ -4,8 +4,8 @@ navTitle: Installing
 ---
 
 PG Failover Slots is supported on the same platforms as the Postgres distribution you're using. Support for PG Failover Slots starts with Postgres 12. For details, see:
-- [EDB Postgres Advanced Server Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas)
 
+- [EDB Postgres Advanced Server Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas)
 - [PostgreSQL Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#pg)
 - [EDB Postgres Extended Server Product Compatibility](https://www.enterprisedb.com/resources/platform-compatibility#epas_extended)
 
@@ -26,20 +26,18 @@ Before you begin the installation process:
 
   To set up the repository, go to [EDB repositories](https://www.enterprisedb.com/repos-downloads), and follow the instructions provided there.
 
-
-
 ## Install the package
 
 The syntax for the RPM package install command is:
 
 ```shell
-sudo <package-manager> -y install pg-<postgres><postgres_version>-pg-failover_slots<major_version>
+sudo <package-manager> -y install pg-<postgres><postgres_version>-pg-failover-slots<major_version>
 ```
 
 The syntax for the Debian package install command is:
 
 ```shell
-sudo <package-manager> -y install pg-<postgres><postgres_version>-pg-failover_slots-<major_version>
+sudo <package-manager> -y install pg-<postgres><postgres_version>-pg-failover-slots-<major_version>
 ```
 
 Where: 
@@ -67,12 +65,12 @@ Where:
 For example, to install PG Failover Slots 1.0.0 for EDB Postgres Advanced Server 15 on a RHEL 8 platform:
 
 ```shell
-sudo dnf -y install pg-as15-pg-failover_slots
+sudo dnf -y install pg-as15-pg-failover-slots1
 ```
 
 To install PG Failover Slots 1.0.0 for EDB Postgres Advanced Server 15 on a Debian 11 platform:
 
 ```shell
-sudo apt-get -y install pg-as15-pg-failover_slots-1
+sudo apt-get -y install pg-as15-pg-failover-slots-1
 ```
 

docker/images/Dockerfile.pdf-builder

@@ -1,9 +1,12 @@
 FROM node:bullseye as base
 
+ARG TARGETARCH
 ARG PANDOC_VERSION=2.14.1
-ARG PANDOC_DEB=pandoc-${PANDOC_VERSION}-1-amd64.deb
+ARG PANDOC_DEB=pandoc-${PANDOC_VERSION}-1-${TARGETARCH}.deb
 ARG WKHTML_TO_PDF_VERSION=0.12.6.1-2
-ARG WKHTML_TO_PDF_DEB=wkhtmltox_${WKHTML_TO_PDF_VERSION}.bullseye_amd64.deb
+ARG WKHTML_TO_PDF_DEB=wkhtmltox_${WKHTML_TO_PDF_VERSION}.bullseye_${TARGETARCH}.deb
+
+RUN echo "Building for ${TARGETARCH}"
 
 # Install Node dependencies 
 RUN npm install -g npm@7

product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx

@@ -0,0 +1,37 @@
+---
+title: Creating an extreme-high-availability cluster
+---
+
+When you create an extreme-high-availability cluster, you need to set up the data group. Extreme-high-availability clusters can contain one or two data groups. 
+
+1. After specifying **Extreme High Availability** as your cluster type on the **Cluster Info** tab and your cluster name and password on the **Cluster Settings** tab, select **Next: Data Groups**. 
+
+1. On the **Nodes Settings** tab, in the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**.  
+
+     For more information on node architecture, see [Extreme high availability (Preview)](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview).
+
+1. In the **Database Type** section:
+
+   1.  Select the type of Postgres you want to use in the **Postgres Type** field:
+
+        -   **Oracle Compatible** is powered by [EDB Postgres Advanced Server](/epas/latest/). View [a quick demonstration of Oracle compatibility on BigAnimal](../../using_cluster/06_demonstration_oracle_compatibility). EDB Postgres Advanced Server is compatible with all three cluster types.
+
+    1.  In the **Postgres Version** list, select either 14 or 15 as the version of Postgres that you want to use. 
+
+1. Select the settings for your cluster according to [Creating a cluster](/biganimal/latest/getting_started/creating_a_cluster/). Find the instructions for the **Node Settings** tab in [Cluster Settings tab](../creating_a_cluster/#cluster-settings-tab) and [Additional Settings tab](../creating_a_cluster/#additional-settings-tab).
+
+1. In the **Parameters** section on the **DB Configuration** tab, you can update the value of the database configuration parameters for the data group as needed.
+
+    To update the parameter values, see [Modifying your database configuration parameters](../../using_cluster/03_modifying_your_cluster/05_db_configuration_parameters).
+
+1. Select **Create: Data Group**. The data group preview appears. 
+
+1. To finish creating your cluster, select **Create Cluster**. If you want to create a second data group, select **Add a Data Group**.
+
+## Creating a second data group
+
+After creating the first data group, you can create a second data group for your extreme-high-availability cluster by selecting **Add a Data Group** before you create the cluster. 
+
+By default, the settings for your first data group populate the second data group's settings. However, if you want to change certain settings you can. Just know that your changes can change the settings for the entire cluster. That being said, the database type and cloud provider must be consistent across both data groups. The data groups and the witness group must all be in different regions. Otherwise, you can choose the second data group's settings as needed. 
+
+When choosing the number of data nodes for the second data group, see [Extreme high availability (Preview)](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview) for information on node architecture.

product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx

@@ -36,7 +36,7 @@ Before creating your cluster, make sure you have enough resources. Without enoug
 
     -  [High availability](/biganimal/latest/overview/02_high_availability/#high-availability) creates a cluster with one primary and one or two standby replicas in different availability zones. You can create high-availability clusters running EDB Postgres Advanced Server or PostgreSQL. Only high-availability clusters allow you to enable read-only workloads for users. However, if you enable read-only workloads, then you might have to raise the IP address resource limits for the cluster. 
 
-    -  [Extreme high availability (beta)](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) creates a cluster configured with a leader node, three shadow nodes, and one witness node. This cluster uses EDB Postgres Distributed to deliver higher performance and faster recovery. You can create extreme high-availability clusters with either PostgreSQL or Oracle compatibility. 
+    -  [Extreme high availability (Preview)](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-preview) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions. This cluster uses EDB Postgres Distributed to deliver higher performance and faster recovery. See [Creating an extreme high-availability cluster](creating_an_eha_cluster) for instructions. 
 
     See [Supported cluster types](/biganimal/latest/overview/02_high_availability/) for more information about the different cluster types.
 
@@ -62,8 +62,6 @@ Before creating your cluster, make sure you have enough resources. Without enoug
         -   **Oracle Compatible** is powered by [EDB Postgres Advanced Server](/epas/latest/). View [a quick demonstration of Oracle compatibility on BigAnimal](../../using_cluster/06_demonstration_oracle_compatibility). EDB Postgres Advanced Server is compatible with all three cluster types.
 
         -   **[PostgreSQL](/supported-open-source/postgresql/)** is an open-source, object-relational database management system. PostgreSQL is compatible with single-node and high-availability cluster types.
-
-        -   **PostgreSQL Compatible** uses advanced logical replication of data and schema. It's available only if you select extreme high availability as your cluster type.
 
     1.  In the **Postgres Version** list, select the version of Postgres that you want to use. See [Database version policy](../../overview/05_database_version_policy) for more information.
 
@@ -87,7 +85,7 @@ Before creating your cluster, make sure you have enough resources. Without enoug
        - For Azure, in **Volume Type**, select **Premium SSD** or **Ultra Disk**. Compared to Premium SSD volumes, ultra disks offer lower-latency, high-performance options and direct control over your disk's input/output operations per second (IOPS). For BigAnimal, we recommend using ultra disks for workloads that require the most demanding performance. See [Using Azure ultra disks](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-enable-ultra-ssd?tabs=azure-portal) for more information. 
           - For Premium SSD, in **Volume Properties**, select the type and amount of storage needed for your cluster. See [Azure Premium SSD storage types](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssds) for more information. 
 
-          - For ultra disk, in **Volume Properties**, select the disk size and IOPS for your cluster. BigAnimal calculates the throughput based on your IOPS settings. 
+          - For ultra disk, in **Volume Properties**, select the disk size and IOPS for your cluster. BigAnimal calculates disk throughput based on your IOPS settings, but you have the option of updating the value. 
 
            !!!important
            While setting the required IOPS for the disk that you selected, consider the VM limits that are tied to the VM size that you selected. See [Ultra disk IOPS](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#ultra-disk-iops) for more information.