Merge pull request #4717 from EnterpriseDB/release/2023-08-29

Release: 2023-08-29
EnterpriseDB · Aug 29, 2023 · d8193fc · d8193fc · github-actions · Aug 29, 2023
2 parents d8d6937 + a0b8c6a
commit d8193fc
Show file tree

Hide file tree

Showing 10 changed files with 51 additions and 41 deletions.
diff --git a/...iganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx b/...iganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx
@@ -8,20 +8,19 @@ When you create a distributed high-availability cluster, you need to set up the
 
 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 [Distributed high availability (Preview)](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview).
+     For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability).
 
 1. In the **Database Type** section:
 
-   1.  Select the type of Postgres you want to use in the **Postgres Type** field:
-
-        -  **[EDB Postgres Advanced Server](/epas/latest/)** is EDB's Oracle-compatible database offering. View [a quick demonstration of Oracle compatibility on BigAnimal](../../using_cluster/06_demonstration_oracle_compatibility).
-
-        - **[EDB Postgres Extended Server](/pge/latest/)** is EDB's advanced logical replication, PostgreSQL-compatible database offering. 
+   1.  Select [EDB Postgres Advanced Server](/epas/latest/) in the **Postgres Type** field:
 
-    1.  In the **Postgres Version** list, select either 14 or 15 as the version of Postgres that you want to use. 
+   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).
 
+   !!!tip
+      When choosing your storage options, for most workloads, consider using at least 20GB of storage. 
+
 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).
@@ -36,7 +35,7 @@ After creating the first data group, you can create a second data group for your
 
 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 [Distributed high availability (Preview)](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview) for information on node architecture.
+When choosing the number of data nodes for the second data group, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) for information on node architecture.
 
 !!! Note
      To maintain high availability, BigAnimal doesn't allow the maintenance windows of data groups to overlap. 
diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx
@@ -16,7 +16,6 @@ Before creating your cluster, make sure you have enough resources. Without enoug
 
 !!!note "When using BigAnimal's cloud"
 The following options aren't available when creating your cluster:
-- Distributed High Availability for cluster type
 - AWS IAM authentication
 - Superuser access
 - PgBouncer 
@@ -44,7 +43,7 @@ The following options aren't available when creating your cluster:
 
     -  [Primary/Standby High Availability](/biganimal/latest/overview/02_high_availability/#primarystandby-high-availability) creates a cluster with one primary and one or two standby replicas in different availability zones. You can create primary/standby high-availability clusters running PostgreSQL or EDB Postgres Advanced Server. Only primary/standby 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. 
 
-    -  [Distributed High Availability (Preview)](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions to deliver higher performance and faster recovery. See [Creating a distributed high-availability cluster](creating_an_eha_cluster) for instructions. 
+    -  [Distributed High Availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) creates a cluster, powered by EDB Postgres Distributed, with up to two data groups spread across multiple cloud regions to deliver higher performance and faster recovery. See [Creating a distributed 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.
 
@@ -95,25 +94,26 @@ The following options aren't available when creating your cluster:
        To maximize your disk size for AWS, select Rb5 as your instance and then io2 Block Express as your storage to get a maximum disk size of 64 TB and 256,000 IOPS.
 
 1.  In the **Storage** section, from the **Volume Type** list, select your volume type. 
-       - 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 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 disk throughput based on your IOPS settings, but you have the option of updating the value. 
+       - 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.
+         !!!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.
 
-       - For AWS, in **Volume Type**, select **General Purpose SSD (GP3)**, **io2**, or **io2 Block Express**.
+    - For AWS, in **Volume Type**, select **General Purpose SSD (GP3)**, **io2**, or **io2 Block Express**.
 
-       !!!Note
-       io2 Block Express is available for selected instance types, such as R5b. However, you can't switch between io2 and io2 Block Express after creating your cluster.
-       !!!  
+      !!!Note
+         io2 Block Express is available for selected instance types, such as R5b. However, you can't switch between io2 and io2 Block Express after creating your cluster.
+      !!!  
 
-        In **Volume Properties**, select the disk size for your cluster, and configure the IOPS.
+      In **Volume Properties**, select the disk size for your cluster, and configure the IOPS.
 
-       - For Google Cloud, in  **Volume Type**, select **SSD Persistent Disk**. 
+    - For Google Cloud, in  **Volume Type**, select **SSD Persistent Disk**. 
 
-        In **Volume Properties**, select the disk size for your cluster, and configure the IOPS.
+       In **Volume Properties**, select the disk size for your cluster, and configure the IOPS.
 
 
 2.  ##### Network, Logs, & Telemetry section

diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx
@@ -7,7 +7,7 @@ redirects:
 BigAnimal supports three cluster types: 
 - Single node
 - Primary/standby high availability
-- Distributed high availability (Preview)
+- Distributed high availability)
 
 You choose the type of cluster you want on the [Create Cluster](https://portal.biganimal.com/create-cluster) page in the [BigAnimal](https://portal.biganimal.com) portal.  
 
@@ -20,7 +20,6 @@ Postgres distribution and version support varies by cluster and deployment type.
 | EDB Postgres Advanced Server | 12–15    | Single-node, primary/standby high-availability | Your cloud account  |
 | EDB Postgres Advanced Server | 14–15    | Single node, primary/standby high availability | BigAnimal cloud account |
 | EDB Postgres Advanced Server | 14–15    | Distributed high-availability      | Your cloud account  |
-| EDB Postgres Extended Server | 14-15    | Distributed high-availability      | Your cloud account  |
 
 ## Single node
 
@@ -56,7 +55,7 @@ To ensure write availability, BigAnimal disables synchronous replication during
 
 Since BigAnimal replicates to only one node synchronously, some standby replicas in three-node clusters might experience replication lag. Also, if you override the BigAnimal synchronous replication configuration, then the standby replicas are inconsistent. 
 
-## Distributed high availability (Preview)
+## Distributed high availability
 
 Distributed high-availability clusters are powered by [EDB Postgres Distributed](/pgd/latest/) using multi-master logical replication to deliver more advanced cluster management compared to a physical replication-based system. Distributed high-availability clusters offer the ability to deploy a cluster across multiple regions or a single region. For use cases where high availability across regions is a major concern, a cluster deployment with distributed high availability enabled can provide one region with three data nodes, another region with the same configuration, and one group with a witness node in a third region for a true active-active solution. 
 

diff --git a/product_docs/docs/biganimal/release/overview/poolers.mdx b/product_docs/docs/biganimal/release/overview/poolers.mdx
@@ -9,14 +9,15 @@ BigAnimal supports [EDB PgBouncer](/pgbouncer/latest/) and [EDB Pgpool-II](/pgpo
 
 EDB PgBouncer can manage your connections to Postgres databases and help your workloads run more efficiently. It's particularly useful if you plan to use more than a few hundred active connections. You can enable EDB PgBouncer to be hosted by BigAnimal when creating your cluster. See [Creating a cluster](/biganimal/latest/getting_started/creating_a_cluster/#pgbouncer). 
 
-!!!note
-   To use PgBouncer when using BigAnimal's cloud account or when creating a distributed high-availability cluster, see the [EDB Pgpool-II documentation](/pgpool/latest/installing).
-
 BigAnimal provisions up to three instances per EDB PgBouncer-enabled cluster to ensure that performance is unaffected, so each availability zone receives its own instance of EDB PgBouncer. 
 
+!!!Note
+   Currently you can't enable EDB PgBouncer when using BigAnimal's cloud account or when creating an  distributed high-availability cluster using your cloud account.
+
 If you want to self-host your EDB PgBouncer deployment, see the [How to configure EDB PgBouncer with BigAnimal cluster](https://support.biganimal.com/hc/en-us/articles/4848726654745-How-to-configure-PgBouncer-with-BigAnimal-Cluster) knowledge-base article.
 
 
+
 ### EDB Pgpool-II
 
 EDB Pgpool-II acts as middleware between client applications and a Postgres database server. It saves connections to the Postgres servers and reuses them whenever a new connection with the same properties (that is, username, database, protocol version) comes in. It reduces connection overhead and improves the system's overall throughput.

diff --git a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx
@@ -8,14 +8,29 @@ BigAnimal calculates the estimated monthly price for your cluster and displays i
 
 ## Database pricing 
 
-Pricing is based on the number of virtual central processing units (vCPUs) provisioned for the database software offering. Consumption of vCPUs is metered hourly. A deployment is typically made up of either one instance or one primary and two standby replica instances of either PostgreSQL or EDB Postgres Advanced Server. When primary/standby high-availability configurations are enabled, multiply the number of vCPUs per instance by the number of replicas configured to calculate the full price for all resources used. This table shows the cost breakdown.
+Pricing is based on the number of virtual central processing units (vCPUs) provisioned for the database software offering. Consumption of vCPUs is metered hourly. 
 
-| Database type                | Hourly price   | Monthly price\* | 
+### Single-node and primary/standby high-availability pricing
+When primary/standby high-availability configurations are enabled, multiply the number of vCPUs per instance by the number of replicas configured to calculate the full price for all resources used. 
+
+This table shows the cost breakdown.
+
+|        Database type         |  Hourly price  | Monthly price\* |                
 | ---------------------------- | -------------- | --------------- | 
-| PostgreSQL                   | $0.0856 / vCPU | $62.49 / vCPU  | 
-| EDB Postgres Advanced Server | $0.2568 / vCPU | $187.46 / vCPU  | 
+| PostgreSQL                   | $0.0856 / vCPU | $62.49 / vCPU   |  
+| EDB Postgres Advanced Server | $0.2568 / vCPU | $187.46 / vCPU |
+
+\* The monthly cost is approximate and assumes 730 hours in a month. 
+
+### Distributed high-availability pricing
+
+When distributed high-availability configurations are enabled, multiply the number of vCPUs per instance by the number of data nodes configured to calculate the full price for all resources used. You aren't charged for the database price for witness nodes or groups in distributed high-availability configurations, just the infrastructure resources, such as compute.
 
-Distributed high availability powered by EDB Postgres Distributed is now available in preview! Contact Sales for more information about pricing.
+This table shows the cost breakdown.
+
+|        Database type         |  Hourly price  | Monthly price\* |                
+| ---------------------------- | -------------- | --------------- | 
+| EDB Postgres Advanced Server | $0.3424 / vCPU | $256.80 / vCPU  |                
 
 \* The monthly cost is approximate and assumes 730 hours in a month. 
 

diff --git a/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx b/product_docs/docs/biganimal/release/reference/cli/managing_clusters.mdx
@@ -137,10 +137,6 @@ __OUTPUT__
 └────────┴───────────────────────────┴──────────┘
 ```
 
-!!!Note
-Distributed high-availability architecture isn't enabled by default. To get access, contact your sales representative or [Support](/biganimal/release/overview/support).
-!!!
-
 !!!Tip
 You can turn off the confirmation step with the `biganimal disable-confirm` command.
 !!!

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
@@ -32,7 +32,7 @@ You can also modify your cluster by installing Postgres extensions. See [Postgre
    | 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 a distributed high-availability cluster)     | **Data Groups**         | &mdash;                                                                                                                                                                                                                                                                                                                                                                     |
+   | Nodes (for a distributed high-availability cluster)  | **Data Groups**         | You can't change the number of data nodes after you create your cluster.                                                                                                                                                                                                                                                                                                                                                                    |
    | 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). |
-Original file line number
+Diff line change
@@ Expand Up / @@ -137,10 +137,6 @@ __OUTPUT__ @@
     └────────┴───────────────────────────┴──────────┘
     ```
-    !!!Note
-    Distributed high-availability architecture isn't enabled by default. To get access, contact your sales representative or [Support](/biganimal/release/overview/support).
-    !!!
     !!!Tip
     You can turn off the confirmation step with the `biganimal disable-confirm` command.
     !!!
@@ Expand Down @@