From f4741efa2a3814cbc0f8b0ae2467e0844f25d249 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Fri, 11 Aug 2023 13:05:55 -0400 Subject: [PATCH 01/10] BigAnimal: PGD GA --- .../creating_a_cluster/creating_an_eha_cluster.mdx | 4 ++-- .../getting_started/creating_a_cluster/index.mdx | 3 +-- .../release/overview/02_high_availability.mdx | 4 ++-- .../biganimal/release/pricing_and_billing/index.mdx | 11 ++++++++--- .../release/reference/cli/managing_clusters.mdx | 4 ---- .../release/using_cluster/04_backup_and_restore.mdx | 2 +- 6 files changed, 14 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx index fc55060c4d4..74d6dec97b3 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx @@ -8,7 +8,7 @@ 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: @@ -36,7 +36,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. \ No newline at end of file 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 index 28f72719af7..809f7e3df41 100644 --- 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. diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 188e2b8151f..6a41a2cb8e4 100644 --- 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. @@ -56,7 +56,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/pricing_and_billing/index.mdx b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx index 468f637b369..ab634a67555 100644 --- a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx +++ b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx @@ -8,15 +8,20 @@ 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. + +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. + +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 an hourly fee for witness nodes or groups in distributed high-availability configurations, only for the infrastructure costs associated with them. + +This table shows the cost breakdown. | Database type | Hourly price | Monthly price\* | | ---------------------------- | -------------- | --------------- | | PostgreSQL | $0.0856 / vCPU | $62.49 / vCPU | +| EDB Postgres Extended Server | $0.1655 / vCPU | $120.82 / VCPU | | EDB Postgres Advanced Server | $0.2568 / vCPU | $187.46 / vCPU | -Distributed high availability powered by EDB Postgres Distributed is now available in preview! Contact Sales for more information about pricing. - \* 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 index 2f97f75a835..5b66fd2016c 100644 --- 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/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx index f8177a82f14..57313f0d4da 100644 --- a/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx @@ -54,6 +54,6 @@ The restore operation is available for any cluster that has at least one availab 1. Select **Next: Data Group**. 1. Select the **Node Settings** tab. 1. In the **Source** section, select **Fully Restore** or **Point in Time Restore**. A point-in-time restore restores the data group as it was at the specified date and time. -1. In the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview). +1. In the **Nodes** section, select **Two Data Nodes** or **Three Data Nodes**. For more information on node architecture, see [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability). 1. Follow Steps 3-5 in [Creating a distributed high-availability cluster](../getting_started/creating_a_cluster/creating_an_eha_cluster/). 1. Select **Restore**. From 4887e1732b9409fd35d4f0ff8e12619b6a562a14 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 14 Aug 2023 14:32:03 -0400 Subject: [PATCH 02/10] incorporating Natalia's feedback --- .../release/pricing_and_billing/index.mdx | 21 ++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx index ab634a67555..6c55cf66b79 100644 --- a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx +++ b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx @@ -10,17 +10,28 @@ BigAnimal calculates the estimated monthly price for your cluster and displays i Pricing is based on the number of virtual central processing units (vCPUs) provisioned for the database software offering. Consumption of vCPUs is metered hourly. +### 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. -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 an hourly fee for witness nodes or groups in distributed high-availability configurations, only for the infrastructure costs associated with them. +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 | + +\* 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. This table shows the cost breakdown. -| Database type | Hourly price | Monthly price\* | +| Database type | Hourly price | Monthly price\* | | ---------------------------- | -------------- | --------------- | -| PostgreSQL | $0.0856 / vCPU | $62.49 / vCPU | -| EDB Postgres Extended Server | $0.1655 / vCPU | $120.82 / VCPU | -| EDB Postgres Advanced Server | $0.2568 / vCPU | $187.46 / vCPU | +| EDB Postgres Extended Server | $0.2511 / vCPU | $188.33 / vCPU | +| EDB Postgres Advanced Server | $0.3424 / vCPU | $256.80 / vCPU | \* The monthly cost is approximate and assumes 730 hours in a month. From cb87eb681ffdee5563bc479539131e83047883e7 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 22 Aug 2023 13:11:08 -0400 Subject: [PATCH 03/10] can't change data nodes (per Natalia) --- .../release/using_cluster/03_modifying_your_cluster/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx b/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx index 69f3e3dfed0..981ea61c664 100644 --- a/product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx +++ b/product_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** | — | + | 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** | — | | 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). | From f27b915aba60973748ae93866d7e602380baaae4 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 23 Aug 2023 08:58:51 -0400 Subject: [PATCH 04/10] adjusted indentation and added storage tip --- .../creating_an_eha_cluster.mdx | 3 +++ .../creating_a_cluster/index.mdx | 25 ++++++++++--------- 2 files changed, 16 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx index 74d6dec97b3..1d43a11f21e 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx @@ -22,6 +22,9 @@ When you create a distributed high-availability cluster, you need to set up the 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). 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 index 809f7e3df41..e3a130a9f58 100644 --- 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 @@ -94,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 From 6cb995bef3c5280b900ec562e373c15ade65af15 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 10:38:15 -0400 Subject: [PATCH 05/10] removed support for PGE --- .../creating_a_cluster/creating_an_eha_cluster.mdx | 8 ++------ .../biganimal/release/overview/02_high_availability.mdx | 1 - .../docs/biganimal/release/pricing_and_billing/index.mdx | 1 - 3 files changed, 2 insertions(+), 8 deletions(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx index 1d43a11f21e..73d108e4f79 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/creating_an_eha_cluster.mdx @@ -12,13 +12,9 @@ When you create a distributed high-availability cluster, you need to set up the 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). diff --git a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx index 6a41a2cb8e4..97b8dfaefb4 100644 --- a/product_docs/docs/biganimal/release/overview/02_high_availability.mdx +++ b/product_docs/docs/biganimal/release/overview/02_high_availability.mdx @@ -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 diff --git a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx index 6c55cf66b79..faa9ab96a08 100644 --- a/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx +++ b/product_docs/docs/biganimal/release/pricing_and_billing/index.mdx @@ -30,7 +30,6 @@ This table shows the cost breakdown. | Database type | Hourly price | Monthly price\* | | ---------------------------- | -------------- | --------------- | -| EDB Postgres Extended Server | $0.2511 / vCPU | $188.33 / vCPU | | EDB Postgres Advanced Server | $0.3424 / vCPU | $256.80 / vCPU | \* The monthly cost is approximate and assumes 730 hours in a month. From 473efb0c0508210d3406b01d4bf8dba344682436 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 13:06:29 -0400 Subject: [PATCH 06/10] removed preview/beta references from PGD docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- product_docs/docs/pgd/5/quickstart/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index ea5c28523f4..ad70985d932 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- EDB BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability powered by EDB Postgres Distributed (PGD) enables single and multi-region Always On clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview) in the [EDB BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account where it's operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of extreme-high-availability support through EDB Postgres Distributed (PGD) allows single-region Always On Gold clusters. These clusters are two PGD groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. diff --git a/product_docs/docs/pgd/5/quickstart/index.mdx b/product_docs/docs/pgd/5/quickstart/index.mdx index 7bd143a9660..a3a691b0075 100644 --- a/product_docs/docs/pgd/5/quickstart/index.mdx +++ b/product_docs/docs/pgd/5/quickstart/index.mdx @@ -20,7 +20,7 @@ navigation: EDB Postgres Distributed (PGD) is a multi-master replicating implementation of Postgres designed for high performance and availability. You can create database clusters made up of many bidirectionally synchronizing database nodes. The clusters can have a number of proxy servers that direct your query traffic to the most available nodes, adding further resilience to your cluster configuration. !!! Note Fully managed BigAnimal - If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/#distributed-high-availability-preview). + If you prefer to have a fully managed EDB Postgres Distributed experience, PGD is now available as an option on BigAnimal, EDB's cloud platform for Postgres. Read more about [BigAnimal distributed high-availability clusters](/biganimal/latest/overview/02_high_availability/#distributed-high-availability). PGD is very configurable. To quickly evaluate and deploy PGD, use this quick start. It'll get you up and running with a fully configured PGD cluster using the same tools that you'll use to deploy to production. This quick start includes: From 355ad67d274eb40dbb551dfca5e2714b89950309 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Mon, 28 Aug 2023 15:37:16 -0400 Subject: [PATCH 07/10] redoing the pooler note --- product_docs/docs/biganimal/release/overview/poolers.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/poolers.mdx b/product_docs/docs/biganimal/release/overview/poolers.mdx index 439a9360f06..1cf43729998 100644 --- a/product_docs/docs/biganimal/release/overview/poolers.mdx +++ b/product_docs/docs/biganimal/release/overview/poolers.mdx @@ -9,13 +9,13 @@ 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. 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. +!!!note + To use PgBouncer when using BigAnimal's cloud account or when creating a distributed high-availability cluster, use the self-hosted method. + ### EDB Pgpool-II From d047b72b1311491e8d61b3d4f899cf86e41f0320 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 29 Aug 2023 07:59:12 -0400 Subject: [PATCH 08/10] reinstating original note re PgBouncer support --- product_docs/docs/biganimal/release/overview/poolers.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/biganimal/release/overview/poolers.mdx b/product_docs/docs/biganimal/release/overview/poolers.mdx index 1cf43729998..c9f70da26bd 100644 --- a/product_docs/docs/biganimal/release/overview/poolers.mdx +++ b/product_docs/docs/biganimal/release/overview/poolers.mdx @@ -11,10 +11,11 @@ EDB PgBouncer can manage your connections to Postgres databases and help your wo 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. -!!!note - To use PgBouncer when using BigAnimal's cloud account or when creating a distributed high-availability cluster, use the self-hosted method. ### EDB Pgpool-II From df22aeb17f21831565384818a23bc84e69b15b25 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 29 Aug 2023 08:07:06 -0400 Subject: [PATCH 09/10] rename in pgd docs --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index ad70985d932..49e4eff4967 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account where it's operated by the Postgres experts. BigAnimal makes it easy to set up, manage, and scale your databases. The addition of extreme-high-availability support through EDB Postgres Distributed (PGD) allows single-region Always On Gold clusters. These clusters are two PGD groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by the Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On Gold clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview. From a0b8c6a0c7dc93c811f917bb5bafb531a1885408 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 29 Aug 2023 08:22:05 -0400 Subject: [PATCH 10/10] missed commit --- product_docs/docs/pgd/5/deployments.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5/deployments.mdx b/product_docs/docs/pgd/5/deployments.mdx index 49e4eff4967..b7ea55a249e 100644 --- a/product_docs/docs/pgd/5/deployments.mdx +++ b/product_docs/docs/pgd/5/deployments.mdx @@ -8,7 +8,7 @@ You can deploy and install EDB Postgres Distributed products using the following - [Trusted Postgres Architect](/tpa/latest) (TPA) is an orchestration tool that uses Ansible to build Postgres clusters using a set of reference architectures that document how to set up and operate Postgres in various scenarios. TPA represents the best practices followed by EDB, and its recommendations apply to quick testbed setups just as they do to production environments. See [Deploying with TPA](tpa) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by the Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On Gold clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility that runs in your cloud account or BigAnimal's cloud account where it's operated by our Postgres experts. EDB BigAnimal makes it easy to set up, manage, and scale your databases. The addition of distributed high-availability support powered by EDB Postgres Distributed (PGD) enables single- and and multi-region Always On Gold clusters. See [Distributed high availability](/biganimal/latest/overview/02_high_availability/#distributed-high-availability) in the [BigAnimal documentation](/biganimal/latest) for more information. - EDB Postgres Distributed for Kubernetes is a Kubernetes operator designed, developed, and supported by EDB. It covers the full lifecycle of highly available Postgres database clusters with a multi-master architecture, using PGD replication. It's based on the open source CloudNativePG operator and provides additional value, such as compatibility with Oracle using EDB Postgres Advanced Server, Transparent Data Encryption (TDE) using EDB Postgres Extended or Advanced Server, and additional supported platforms including IBM Power and OpenShift. This offering is currently in preview.