Merge pull request #2969 from EnterpriseDB/release/2022-07-21

Release: 2022-07-21

advocacy_docs/partner_docs/DBeaverPRO/03-SolutionSummary.mdx

@@ -6,5 +6,5 @@ description: 'Brief explanation of the solution and its purpose'
 DBeaver PRO is a SQL client software application and universal database management tool for EDB Postgres Advanced Server and EDB Postgres Extended Server. With DBeaver PRO you can manipulate your data like you would in a regular spreadsheet. You have the ability to view, create, modify, save, and delete all Postgres data types. The features resemble those of a regular spreadsheet, as you can create analytical reports based on records from different data storages and export information in an appropriate format. DBeaver PRO also provides you with a powerful editor for SQL, data and schema migration, monitoring of database connection sessions, and other administration features.
 
 <p align="center">
-  <img src="Images/DbeaverArc.png">
+  <img src="Images/UpdatedDBeaverArc.png">
 </p>

product_docs/docs/biganimal/release/overview/02_high_availability.mdx

@@ -28,7 +28,7 @@ In case of unrecoverable failure of the primary, a restore from a backup is requ
 
 ![*BigAnimal Cluster4*](images/Single-Node-Diagram-2x.png)
 
-## Standard high availability
+## High availability
 
 The high availability option is provided to minimize downtime in cases of failures. High-availability clusters—one *primary* and one or two *standby replicas*—are configured automatically, with standby replicas staying up to date through physical streaming replication. 
 

product_docs/docs/epas/14/epas_guide/03_database_administration/05_edb_audit_logging/09_object_auditing.mdx

@@ -9,7 +9,7 @@ The object-level auditing allows selective auditing of objects for specific Data
 Use the following syntax to specify an `edb_audit_statement` parameter value for `SELECT`, `UPDATE`, `DELETE`, or `INSERT` statements:
 
 ```text
-{ select | update | delete | insert }@groupname
+{ select | update | delete | insert }{@ | -}groupname
 ```
 
 ## Example

product_docs/docs/migration_portal/4.0/04_mp_migrating_database/03_mp_schema_migration.mdx

@@ -30,8 +30,8 @@ You can migrate schemas to an existing on-premises EDB Postgres Advanced Server
 
 2.  Select one or more schemas to migrate to EDB Postgres Advanced Server.
 
- !!! Note
-     If your schemas aren't 100% compatible, a banner appears. Complete the Contact Us form as needed.
+    !!! Note
+    If your schemas aren't 100% compatible, a banner appears. Complete the Contact Us form as needed.
 
 
 3.  To download the assessed schemas, select **Download SQL file**.
@@ -42,20 +42,20 @@ You can migrate schemas to an existing on-premises EDB Postgres Advanced Server
 
 5.  To import the schemas, run:
 
--   On CLI:
+    -   On CLI:
 
-    ```text
-    \i c:\users\...\<project_name>.sql
-    ```
+        ```text
+        \i c:\users\...\<project_name>.sql
+        ```
 
--   On cmd/shell:
+    -   On cmd/shell:
 
-    ```text
-    edb-psql -f <project_name>.sql
-    ```
+        ```text
+        edb-psql -f <project_name>.sql
+        ```
 
- !!! Note
-    You can alternatively use the `pgAdmin` client for the import.
+    !!! Note
+        You can alternatively use the `pgAdmin` client for the import.
 
 The converted schemas migrate to the target server.
 
@@ -190,18 +190,18 @@ Migrate schemas on EDB Postgres Advanced Server to the cloud.
 
 4.  To launch a new cluster, select **Go to BigAnimal**.
 
- Or, if you have an existing cluster running, select **Next**.
+    Or, if you have an existing cluster running, select **Next**.
 
-  !!! Note
+    !!! Note
     See the [Big Animal](https://www.enterprisedb.com/edb-cloud) page for more information.
 
 5.  Enter the required connection details on the `Connect` page.
 
- ![Connecting to the cloud cluster](../images/mp_migrate_cloud_connection_updated.png)
+    ![Connecting to the cloud cluster](../images/mp_migrate_cloud_connection_updated.png)
 
 7.  To verify the connection details, select **Test Connection**.
 
- !!! Note
+    !!! Note
     You can select **Edit Connection** to make changes to the connection details and retest the connection details.
 
 8.  Once the connection is successful, select **Next**.

product_docs/docs/pgd/3.6/bdr/index.mdx

@@ -0,0 +1,60 @@
+---
+navTitle: BDR
+title: "BDR (Bi-Directional Replication)"
+directoryDefaults:
+  description: "BDR (Bi-Directional Replication) is a ground-breaking multi-master replication capability for PostgreSQL clusters that has been in full production status since 2014."
+---
+
+**BDR (Bi-Directional Replication)** is a ground-breaking multi-master replication capability for PostgreSQL clusters that has been in full production status since 2014. In the complex environment of replication, this 3rd generation of BDR achieves efficiency and accuracy, enabling very high availability of all nodes in a geographically distributed cluster. This solution is for top-tier enterprise applications that require near-zero downtime and near-zero data loss.
+
+As a standard PostgreSQL extension BDR does this through logical replication of data and schema along with a robust set of features and tooling to manage conflicts and monitor performance. This means applications with the most stringent demands can be run with confidence on PostgreSQL.
+
+BDR was built from the start to allow for rolling upgrades and developed in conjunction with partners who were replacing costly legacy solutions.
+
+Available as two editions, BDR Standard provides essential multi-master replication capabilities for delivering row level consistency to address high availability and/or geographically distributed workloads. BDR Enterprise adds advanced conflict-handling and data-loss protection capabilities.
+
+## BDR Enterprise
+
+To provide very high availability, avoid data conflicts, and to cope with more advanced usage scenarios, the Enterprise edition provides the following extensive additional features:
+
+* Eager replication provides conflict free replication by synchronizing across cluster nodes before committing a transaction
+* Commit at most once consistency guards application transactions even in the presence of node failures
+* Conflict-free replicated data types (CRDTs) provide mathematically proven consistency in asynchronous multi-master update scenarios
+* Column level conflict resolution enables per column last-update wins resolution to merge updates
+* Transform triggers execute on incoming data for modifying or advanced programmatic filtering
+* Conflict triggers provide custom resolution techniques when a conflict is detected
+
+BDR Enterprise requires EDB Postgres Extended v11 (formerly known as 2ndQuadrant Postgres) which is SQL and on-disk compatible with PostgreSQL.
+
+!!!note
+  The documentation for the latest stable 3.6 release is available here:
+
+  [BDR 3.6 Enterprise Edition](https://documentation.enterprisedb.com/bdr3-enterprise/release/latest-3.6/)
+
+  **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)**
+!!!
+
+## BDR Standard
+
+The Standard edition provides loosely-coupled multi-master logical replication using a mesh topology. This means that you can write to any node and the changes will be sent directly, row-by-row to all the other nodes that are part of the BDR cluster.
+
+By default BDR uses asynchronous replication to provide row-level eventual consistency, applying changes on the peer nodes only after the local commit.
+
+The following are included to support very high availability and geographically distributed workloads:
+
+* Rolling application and database upgrades to address the largest source of downtime
+* DDL replication supports changes to application schema, ideal for use in continuous release environments
+* Sequence handling provides applications different options for generating unique surrogate ids that a multi-node aware
+* Tools to assess applications, monitor operation, and verify data consistency
+
+BDR Standard requires PostgreSQL v10 or v11.
+
+!!!note
+  The documentation for the latest stable 3.6 release is available here:
+
+  [BDR 3.6 Standard Edition](https://documentation.enterprisedb.com/bdr3/release/latest-3.6/)
+
+   **This is a protected area of our website, if you need access please [contact us](https://www.enterprisedb.com/contact)**
+!!!
+
+

product_docs/docs/pgd/3.6/index.mdx

@@ -0,0 +1,36 @@
+---
+title: "EDB Postgres Distributed"
+---
+
+EDB Postgres Distributed provides loosely-coupled multi-master logical replication
+using a mesh topology. This means that you can write to any server and the
+changes are sent directly, row-by-row to all the
+other servers that are part of the same mesh.
+
+EDB Postgres Distributed consists of several components that make the whole
+cluster work.
+
+## Postgres server
+
+Two different Postgres distributions can be used:
+
+- [PostgreSQL](https://www.postgresql.org/) - open source
+- [EDB Postgres Extended Server](https://techsupport.enterprisedb.com/customer_portal/sw/2ndqpostgres/) - PostgreSQL compatible and optimized for replication
+
+What Postgres distribution and version is right for you depends on the features you need.
+See the feature matrix in [Choosing a Postgres distribution](/pgd/latest/choosing_server) for detailed comparison.
+
+
+## [BDR](bdr)
+
+A Postgres server with the [BDR](bdr) extension installed is referred to as a BDR
+node. BDR nodes can be either data nodes or witness nodes.
+
+Witness nodes don't participate in data replication and are only used as a
+tie-breaker for consensus.
+
+
+## [pglogical 3](pglogical)
+
+BDR depends on [pglogical 3](pglogical) to provide the replication
+channel upon which BDR builds.