diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/02-PartnerInformation.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/02-PartnerInformation.mdx index e828a4270e8..5a8b142c52a 100644 --- a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/02-PartnerInformation.mdx +++ b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/02-PartnerInformation.mdx @@ -1,6 +1,6 @@ --- title: 'Partner Information' -description: 'Details for and ' +description: 'Details for (Partner Name) (Partner Product)' --- |   |   | @@ -8,5 +8,5 @@ description: 'Details for and ' | **Partner Name** | | | **Partner Product** | | | **Web Site** | | -| **Version & Platform** | | -| **Product Description** | | +| **Version** | | +| **Product Description** | | diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/03-SolutionSummary.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/03-SolutionSummary.mdx index b7eef28a184..e1f03510ffd 100644 --- a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/03-SolutionSummary.mdx +++ b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/03-SolutionSummary.mdx @@ -2,13 +2,10 @@ title: 'Solution Summary' description: 'Brief explanation of the solution and its purpose' --- -(Insert explanation of solution and diagram of solution below) - -

- -

+(Insert explanation of solution and diagram of solution below) +![Placeholder Image](Images/PlaceholderImage.png) !!! Note - (Insert text for your note here) \ No newline at end of file + (Insert text for your note here) diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringPartnerNamePartnerProduct.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringPartnerNamePartnerProduct.mdx new file mode 100644 index 00000000000..f99a65270b3 --- /dev/null +++ b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringPartnerNamePartnerProduct.mdx @@ -0,0 +1,12 @@ +--- +title: 'Configuring (Partner Name) (Partner Product)' +description: 'Walkthrough on configuring (Partner Name) (Partner Product)' +--- + +Implementing (Partner Name) (Partner Product) with (EDB Product) requires the following components: + +- +- +- + + diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringTheIntegration.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringTheIntegration.mdx deleted file mode 100644 index c969c1133ce..00000000000 --- a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/04-ConfiguringTheIntegration.mdx +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: 'Configuring the Integration' -description: 'Walkthrough on configuring ' ---- - -(Insert implementation instructions here): - -- -- -- - -### Prerequisites - -### Configuring (PartnerProductName) - -### Installing (PartnerProductName) diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerName.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerName.mdx deleted file mode 100644 index 4d99ebb9b9b..00000000000 --- a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerName.mdx +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: 'Using ' -description: 'Walkthroughs of example usage scenarios' ---- - -### Sample User Scenarios -(Insert product use cases here) \ No newline at end of file diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerNamePartnerProduct.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerNamePartnerProduct.mdx new file mode 100644 index 00000000000..445a0681a94 --- /dev/null +++ b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/05-UsingPartnerNamePartnerProduct.mdx @@ -0,0 +1,35 @@ +--- +title: 'Using (Partner Name) (Partner Product)' +description: 'Walkthroughs of multiple (Partner Name) (Partner Product) usage scenarios' +--- + +The examples below will walk you though some of the common usage scenarios that can be used with (EDB Product Name). These are examples to help get you started and show how the products can work together. + +1. Usage case one + - blank + - blank + - blank +2. Usage case two + - blank + - blank + - blank + +## Usage case one + +1. blank + + ![Placeholder Image](Images/PlaceholderImage.png) + +2. blank + + ![Placeholder Image](Images/PlaceholderImage.png) + +## Usage case two + +1. blank + + ![Placeholder Image](Images/PlaceholderImage.png) + +2. blank + + ![Placeholder Image](Images/PlaceholderImage.png) diff --git a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/06-CertificationEnvironment.mdx b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/06-CertificationEnvironment.mdx index 86e224d94d1..9171d9f3674 100644 --- a/advocacy_docs/partner_docs/Markdown Implementation Guide Template/06-CertificationEnvironment.mdx +++ b/advocacy_docs/partner_docs/Markdown Implementation Guide Template/06-CertificationEnvironment.mdx @@ -1,28 +1,11 @@ --- title: 'Certification Environment' -description: 'Overview of the certification environment used in the certification of ' +description: 'Overview of the certification environment used in the certification of (Partner Name) (Partner Product)' --- |   |   | | ----------- | ----------- | | **Certification Test Date** | | | **EDB Postgres Advanced Server** | | -| **OS** | | -| **Memory** | | -| **Processor** | | -| **Cloud Platform** | | -| **CPU(s)** | | -| **Core(s) per socket** | | -| **Socket(s)** | | -| **Storage** | | -| **(Partner Product Name)** | | - - -|   |   | -| ----------- | ----------- | -| **Certification Test Date**| | -| **BDR-Always-ON**| | -| **OS**| | -| **Cloud Platform**| | -| **Deployment Tool**| | -| **(Partner Product Name)** | | +| **EDB Postgres Extended Server** | | +| **(Partner Name) (Partner Product)** | | diff --git a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx index d98aad88709..c4c705e83f2 100644 --- a/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/02_connecting_to_your_cloud/index.mdx @@ -30,53 +30,44 @@ Before connecting to your cloud, - bash shell version 4.0 or above. - [jq](https://stedolan.github.io/jq/) JSON parser. + - BigAnimal CLI version 1.4 or later. For detailed steps, see [Installing the CLI](../../reference/cli/#installing-the-cli). + - Be aware that BigAnimal requires permissions to run Kubernetes cluster services for PostgreSQL workloads and the associated storage services. It requires a set of supporting permissions: + + - Services for monitoring and logging to produce service telemetry information. + + - To set up networking so PostgreSQL workloads are reachable by customer applications and telemetry data is collected. + + - To provision vaults for safe storage of data at rest encryption keys. + + - To create workload identities and manage their permissions. + + - And, a small set of supporting permissions to ensure access to the services above and availability of cloud account information. + + The scope of these permissions are limited to the associated cloud account. + - Ensure that the BigAnimal login user running the CLI is assigned either the owner or the contributor role. Perform the following steps: 1. Open the [Azure Cloud Shell](https://shell.azure.com/) or the [AWS Cloud Shell](https://console.aws.amazon.com/cloudshell) in your browser. -1. Log in to BigAnimal as a user with either the owner or the contributor role. +1. Create a BigAnimal CLI credential: ```shell - biganimal create-credential --name --address portal.biganimal.com --port 443 + ./biganimal create-credential --name --address portal.biganimal.com --port 443 ``` -1. Run the `setup-csp` command to set up your cloud provider. The synatx is: +1. Run the `setup-csp` command to set up your cloud provider: ```shell - setup-csp --provider - {--account-id | --subscription-id} - --region - [--instance-type --cluster-architecture --networking | --skip-preflight] - [--run] + ./biganimal setup-csp ``` !!! Important Do not delete the `ba-passport.json` file created in your working directory. It contains important identity and access management information used by `connect-csp` while connecting to your cloud. - Here is an example of setting up an AWS account: - - ```shell - biganimal setup-csp --provider aws --account-id 123456789102 --region us-east-1 --instance-type aws:r5.large --cluster-architecture ha --networking private --run - ``` - - Here is an example if setting up an Azure account: - ```shell - biganimal setup-csp --provider azure --subscription-id abc12345-1234-1234-abcd-12345678901 --region eastus --instance-type azure:Standard_E4s_v3 --cluster-architecture ha --networking private --run - ``` - - For more information on the command arguments, run the following command: - - ```shell - biganimal setup-csp --help - ``` - - Alternatively, you can enable the CLI interactive mode to have the CLI guide you through the process: - ```shell - biganimal config set interactive_mode on - biganimal setup-csp - ``` + + !!! Tip Your organization might require you to review the scripts that are invoked while setting up your cloud account. To generate the scripts invoked by `setup-csp`, execute the command without the `--run` option. You can now review and manually execute `ba-csp-preflight` and then `ba-csp-setup` from your working directory. @@ -91,6 +82,6 @@ Perform the following steps: 1. If the cloud readiness checks pass, your cloud account is successfully set up. Connect your cloud account to BigAnimal with following command. ```shell - biganimal connect-csp --provider + ./biganimal connect-csp --provider ``` Once your cloud account is successfully connected to BigAnimal, you, and other users with the correct permissions, can create clusters. \ No newline at end of file diff --git a/product_docs/docs/biganimal/release/getting_started/index.mdx b/product_docs/docs/biganimal/release/getting_started/index.mdx index 65d7845dc25..2d4c8d93d06 100644 --- a/product_docs/docs/biganimal/release/getting_started/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/index.mdx @@ -5,8 +5,8 @@ navigation: - 00_free_trial - identity_provider - 02_azure_market_setup - - 02_connecting_to_your_cloud - preparing_cloud_account + - 02_connecting_to_your_cloud - creating_a_cluster --- diff --git a/product_docs/docs/biganimal/release/reference/cli.mdx b/product_docs/docs/biganimal/release/reference/cli.mdx index 9b580869a08..357fc56c5f4 100644 --- a/product_docs/docs/biganimal/release/reference/cli.mdx +++ b/product_docs/docs/biganimal/release/reference/cli.mdx @@ -39,6 +39,14 @@ The CLI is available for Linux, MacOS, and Windows operating systems. echo "$( -Use the `primary.shutdown.as.failure` property to treat any shutdown of the Failover Manager agent on the primary node as a failure. If this property is set to `true` and the primary agent is shut down, the rest of the cluster treats the shutdown as a failure. This includes any proper shutdown of the agent such as a shutdown of the whole node. None of the timeout properties apply in this case: when the agent exits, the rest of the cluster is notified immediately. After the agent exits, the rest of the cluster performs the regular failover steps that happen in the case of agent failure. The regular failover steps include attempting to connect to the primary database, seeing if the VIP is reachable if used, and so on). +Use the `primary.shutdown.as.failure` property to treat any shutdown of the Failover Manager agent on the primary node as a failure. If this property is set to `true` and the primary agent is shut down, the rest of the cluster treats the shutdown as a failure. This includes any proper shutdown of the agent such as a shutdown of the whole node. None of the timeout properties apply in this case: when the agent exits, the rest of the cluster is notified immediately. After the agent exits, the rest of the cluster performs [checks](../11_supported_scenarios/#primary_agent_exits) that happen in the case of a primary agent failure. The [checks](../11_supported_scenarios/#primary_agent_exits) include attempting to connect to the primary database, seeing if the VIP is reachable if used, and so on). - If the database is reached, a notification is sent informing you of the agent status. - If the database isn't reached, a failover occurs. diff --git a/product_docs/docs/efm/4/07_using_efm_utility.mdx b/product_docs/docs/efm/4/07_using_efm_utility.mdx index 97f8309b443..827fec01db3 100644 --- a/product_docs/docs/efm/4/07_using_efm_utility.mdx +++ b/product_docs/docs/efm/4/07_using_efm_utility.mdx @@ -108,7 +108,7 @@ Invoke the `efm encrypt` command to encrypt the database password before includi The `efm promote` command instructs Failover Manager to perform a manual failover of standby to primary. -Attempt manual promotion only if the status command reports that the cluster includes a standby node that is up to date with the primary. If there is no up-to-date standby, Failover Manager prompts you before continuing. +Attempt a manual promotion only during a maintenance window for your database cluster and if the status command reports that all standbys in the cluster are up to date with the primary. Include the `–switchover` clause to promote a standby node and reconfigure a primary node as a standby node. Include the `-sourcenode` keyword, and specify a node address to indicate the node whose recovery settings to copy to the old primary node, which makes it a standby. Include the `-quiet` keyword to suppress notifications during the switchover process. Include the `-noscripts` keyword to instruct Failover Manager not to invoke fencing or post-promotion scripts. diff --git a/product_docs/docs/epas/14/epas_rel_notes/20_epas14_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/20_epas14_rel_notes.mdx index 03e2b62c4ec..834b1e5b0ad 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/20_epas14_rel_notes.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/20_epas14_rel_notes.mdx @@ -5,30 +5,30 @@ title: "Version 14.1.0" New features, enhancements, bug fixes, and other changes in EDB Postgres Advanced Server 14 include: -| Type | Category | Description | -| --------------- | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream merge | | See the [PostgreSQL 14 Release Notes](https://www.postgresql.org/docs/14/release-14.html) for more information. See also [PostgreSQL 14 Open Items](https://wiki.postgresql.org/wiki/PostgreSQL_14_Open_Items). | -| Feature | Oracle compatibility | Added the `SUBPARTITION TEMPLATE` clause, so that there is no need to specify the subpartition descriptor or each partition. Specify the `TEMPLATE` once and it gets applied to every partition automatically. | -| Feature | Oracle compatibility |Enabled access to a partition by `PARTITION ()` or subpartition by `SUBPARTITION ()` clause, which allows the use of such clauses for `SELECT`, `UPDATE`, `INSERT`, and `DELETE` queries. | -| Feature | Oracle compatibility | Added support for `USERENV()`, a function providing user environment and session related details. | -| Feature | Oracle compatibility | Added support for bitwise `AND` and `OR` functions and aggregates operation on a numeric data type and added bitwise `&` and `\|` operators for the numeric data types. | -| Feature | Oracle compatibility | Added support for the `NOCYCLE` and `ENABLE` keywords. -| Feature | Oracle compatibility | Generalized `CONNECT_BY` syntax support:
- Allow the use of multiple `PRIOR` expressions.
- Use `AND/OR` with multiple conditions to allow any combination of Unary, Binary or Prior expressions.
- Use of Unary expressions.
- Make `PRIOR` optional with `CONNECT BY` query.
- Enhance the function to detect the cycle, so that it can work with multiple `PRIOR` expressions.
- Support `PRIOR` in the target list. | -| Feature | Oracle compatibility | Enhanced `NVL2` to use `ANYCOMPATIBLE` pseudo-type. Allows the `NVL2` function to support considerably more argument-type combinations. For example, the `NVL2` version can match a call with one `INTEGER` and multiple `BIGINT` arguments and the `INTEGER` is automatically promoted to `BIGINT`. With the previous `ANYELEMENT` version, you had to cast the `INTEGER` explicitly. | -| Feature | Oracle compatibility | Added traceability for when an object is created and last modified by a DDL operation. | -| Feature | Oracle compatibility | When a user tries to create a sequence with an upper boundary out of range, a warning message is logged. | -| Feature | Oracle compatibility | When a user creates a sequence specifying the `NOORDER` keyword, the keyword is considered a `NOOP` keyword and a warning message is logged which states that specifying the `NOORDER` keyword has no beneficial effect in EDB Postgres Advanced and is ignored. | -| Feature | Oracle compatibility | Trailing zeros with `TO_CHAR(numeric)` are removed to be more compatible with Oracle. | -| Feature | Oracle compatibility | Added support for using an alias on table names in `INSERT` statements for accessing a partition or subpartition with `SELECT`, `INSERT`, `UPDATE`, or `DELETE` statements, so that the alias can be used to qualify the table columns. For example, `INSERT INTO table_name t (t.col1) VALUES (10);` | -| Feature | Oracle compatibility | Enhanced `DBMS_SQL` package functions to accept `NUMBER` instead of `INTEGER` so that both `INTEGER` to `NUMBER` functions can accept both `NUMBER` and `INTEGER` type values. Since these functions are compatible with both `NUMBER` and `INTEGER`, EDB Postgres Advanced Server restricts the input range within the `INTEGER`'s limit. | -| Feature | Security | Added support for selective auditing of objects for specific DML statements such as `SELECT`, `INSERT`, `UPDATE`, or `DELETE` and to specify either include `(@)` or exclude `(-)` particular statement type for a relation. For more information see [Object Auditing](../epas_guide/03_database_administration/05_edb_audit_logging/09_object_auditing/). | -| Feature | Security |Added capability to control the space consumed by the audit log directory and to manage the audit log files, which can be configured through a new `edb_audit_archiver` configuration parameter. The `edb_audit_archiver` parameter helps in compressing the old audit log files by specifying the compression command and executing the command before removing the old audit log files. | -| Feature | Security | Provided an option to audit the `SET` commands. To enable this you need to modify the `log_statement` GUC. | -| Feature | General functionality | Enabled creation of `ROWID` columns with `IMPORT FOREIGN SCHEMA`. | | Feature | General Functionality | Began using global sequences for the ROWIDs so that they are unique across the database and can be used on the partitioned tables. | -| Feature | General functionality | Began using global sequences for `ROWID` so that they are unique across the database and can be used on the partitioned tables. | | Feature | General Functionality | Began using global sequences for the ROWIDs so that they are unique across the database and can be used on the partitioned tables. | -| Feature | General functionality | Allowed dynamic partition creation to non-owner insert queries. | -| Feature | General functionality | Extended `\h` support to work with EDB Postgres Advanced Server objects so that users can see the syntax on a `psql` prompt. | -| Feature | General functionality | Added tab-completion support for EDB Postgres Advanced Server syntaxes. +| Type | Category | Description | +| -------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Upstream merge | | See the [PostgreSQL 14 Release Notes](https://www.postgresql.org/docs/14/release-14.html) for more information. See also [PostgreSQL 14 Open Items](https://wiki.postgresql.org/wiki/PostgreSQL_14_Open_Items). | +| Feature | Oracle compatibility | Added the `SUBPARTITION TEMPLATE` clause, so that there is no need to specify the subpartition descriptor or each partition. Specify the `TEMPLATE` once and it gets applied to every partition automatically. | +| Feature | Oracle compatibility | Enabled access to a partition by `PARTITION ()` or subpartition by `SUBPARTITION ()` clause, which allows the use of such clauses for `SELECT`, `UPDATE`, `INSERT`, and `DELETE` queries. | +| Feature | Oracle compatibility | Added support for `USERENV()`, a function providing user environment and session related details. | +| Feature | Oracle compatibility | Added support for bitwise `AND` and `OR` functions and aggregates operation on a numeric data type and added bitwise `&` and `\` operators for the numeric data types. | +| Feature | Oracle compatibility | Added support for the `NOCYCLE` and `ENABLE` keywords. | +| Feature | Oracle compatibility | Generalized `CONNECT_BY` syntax support:
- Allow the use of multiple `PRIOR` expressions.
- Use `AND/OR` with multiple conditions to allow any combination of Unary, Binary or Prior expressions.
- Use of Unary expressions.
- Make `PRIOR` optional with `CONNECT BY` query.
- Enhance the function to detect the cycle, so that it can work with multiple `PRIOR` expressions.
- Support `PRIOR` in the target list. | +| Feature | Oracle compatibility | Enhanced `NVL2` to use `ANYCOMPATIBLE` pseudo-type. Allows the `NVL2` function to support considerably more argument-type combinations. For example, the `NVL2` version can match a call with one `INTEGER` and multiple `BIGINT` arguments and the `INTEGER` is automatically promoted to `BIGINT`. With the previous `ANYELEMENT` version, you had to cast the `INTEGER` explicitly. | +| Feature | Oracle compatibility | Added traceability for when an object is created and last modified by a DDL operation. | +| Feature | Oracle compatibility | When a user tries to create a sequence with an upper boundary out of range, a warning message is logged. | +| Feature | Oracle compatibility | When a user creates a sequence specifying the `NOORDER` keyword, the keyword is considered a `NOOP` keyword and a warning message is logged which states that specifying the `NOORDER` keyword has no beneficial effect in EDB Postgres Advanced and is ignored. | +| Feature | Oracle compatibility | Trailing zeros with `TO_CHAR(numeric)` are removed to be more compatible with Oracle. | +| Feature | Oracle compatibility | Added support for using an alias on table names in `INSERT` statements for accessing a partition or subpartition with `SELECT`, `INSERT`, `UPDATE`, or `DELETE` statements, so that the alias can be used to qualify the table columns. For example, `INSERT INTO table_name t (t.col1) VALUES (10);` | +| Feature | Oracle compatibility | Enhanced `DBMS_SQL` package functions to accept `NUMBER` instead of `INTEGER` so that both `INTEGER` to `NUMBER` functions can accept both `NUMBER` and `INTEGER` type values. Since these functions are compatible with both `NUMBER` and `INTEGER`, EDB Postgres Advanced Server restricts the input range within the `INTEGER`'s limit. | +| Feature | Security | Added support for selective auditing of objects for specific DML statements such as `SELECT`, `INSERT`, `UPDATE`, or `DELETE` and to specify either include `(@)` or exclude `(-)` particular statement type for a relation. For more information see [Object Auditing](../epas_guide/03_database_administration/05_edb_audit_logging/09_object_auditing/). | +| Feature | Security | Added capability to control the space consumed by the audit log directory and to manage the audit log files, which can be configured through a new `edb_audit_archiver` configuration parameter. The `edb_audit_archiver` parameter helps in compressing the old audit log files by specifying the compression command and executing the command before removing the old audit log files. | +| Feature | Security | Provided an option to audit the `SET` commands. To enable this you need to modify the `log_statement` GUC. | +| Feature | General functionality | Enabled creation of `ROWID` columns with `IMPORT FOREIGN SCHEMA`. | +| Feature | General functionality | Began using global sequences for `ROWID` so that they are unique across the database and can be used on the partitioned tables. | +| Feature | General functionality | Allowed dynamic partition creation to non-owner insert queries. | +| Feature | General functionality | Extended `\h` support to work with EDB Postgres Advanced Server objects so that users can see the syntax on a `psql` prompt. | +| Feature | General functionality | Added tab-completion support for EDB Postgres Advanced Server syntaxes. | ## Included components diff --git a/product_docs/docs/pgd/4/deployments/index.mdx b/product_docs/docs/pgd/4/deployments/index.mdx index e2c122e85a9..839597db544 100644 --- a/product_docs/docs/pgd/4/deployments/index.mdx +++ b/product_docs/docs/pgd/4/deployments/index.mdx @@ -8,9 +8,9 @@ You can deploy and install EDB Postgres Distributed products using the following - TPAexec is an orchestration tool that uses Ansible to build Postgres clusters as specified by TPA (Trusted Postgres Architecture), 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 are as applicable to quick testbed setups as to production environments. -Coming soon: +- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account and 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 Postres Distributed allows single-region Always On Gold clusters: two BDR groups in different availability zones in a single cloud region, with a witness node in a third availability zone. See the [Extreme high availability](/biganimal/latest/overview/02_high_availability/#extreme-high-availability-beta) topic in the [BigAnimal documentation](/biganimal/latest) for more information. -- BigAnimal is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account and 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 Postres Distributed allows single-region Always On Gold clusters: two BDR groups in different availability zones in a single cloud region, with a witness node in a third availability zone. +Coming soon: - EDB Postgres Distributed for Kubernetes will be a Kubernetes operator is designed, developed, and supported by EDB that covers the full lifecycle of a highly available Postgres database clusters with a multi-master architecture, using BDR replication. It is based on the open source CloudNativePG operator, and provides additional value such as compatibility with Oracle using EDB Postgres Advanced Server and additional supported platforms such as IBM Power and OpenShift.