Merge pull request #3110 from EnterpriseDB/release/2022-09-01

Release: 2022-09-01

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

@@ -73,6 +73,8 @@ Prior to creating your cluster, make sure you have enough resources. Without eno
        - Compute optimized for compute bound applications
        - General purpose if you don't require memory or compute optimization. 
     1. Select the instance series and size. See [Sizes for virtual machines in Azure](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes) or [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/) for information to help you choose the appropriate instance type. 
+       !!!tip
+       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, select your volume type from the **Volume Type** list. 
     - For Azure, in **Volume Type** select either 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 IOPS (input/output operations per second). BigAnimal recommends 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. 
@@ -83,14 +85,13 @@ Prior to creating your cluster, make sure you have enough resources. Without eno
         !!!important
         While setting the required IOPS for the disk you should consider the VM limits that are tied to the VM size that you have 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 either General Purpose SSD (GP3), io2, or io2 Block Express.
+    - For AWS, in **Volume Type** select either General Purpose SSD (GP3), io2, or io2 Block Express. 
 
-     !!!Note
+      !!!Note
          io2 Block Express is available for selected instance types (such as R5b). However, you cannot 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.
 
-
 1.  In the **Networking Connectivity** section, you specify whether to use private or public networking. Networking is set to **Public** by default. Public means that any client can connect to your cluster’s public IP address over the internet. Optionally, you can limit traffic to your public cluster by specifying an IP allowlist, which allows access only to certain blocks of IP addresses. To limit access, add one or more classless inter-domain routing (CIDR) blocks in the **IP Allowlists** section. CIDR is a method for allocating IP addresses and IP routing to a whole network or subnet. If you have any CIDR block entries, access is limited to those IP addresses. If none are specified, all network traffic is allowed. 
 
     Private networking allows only IP addresses within your private network to connect to your cluster. See [Cluster networking architecture](01_cluster_networking) for more information.

product_docs/docs/efm/4/efm_rel_notes/index.mdx

@@ -9,7 +9,7 @@ about the release that introduced the feature.
 
 | Version | Release Date |
 | ------- | ------------ |
-| [4.5](05_efm_45_rel_notes) | 2022 Aug 31 |
+| [4.5](05_efm_45_rel_notes) | 2022 Aug 30 |
 | [4.4](06_efm_44_rel_notes) | 2022 Jan 5 |
 | [4.3](07_efm_43_rel_notes) | 2021 Dec 18|
 | [4.2](08_efm_42_rel_notes) | 2021 Apr 19|

product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx

@@ -329,7 +329,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
- Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+ Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres` and the name of the default database will be `postgres`. The few Advanced Server’s features compatible with Oracle databases will be available with this mode. However, we recommend using the Advanced server in redwood compatibility mode to use all its features.
 
 `--redwood-like`
 

product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx

@@ -47,17 +47,15 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using the Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
 
 `--redwood-like`
 
-Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
 
 `--icu-short-form`
 
-Include the `--icu-short-form` keywords to create a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, please refer to the *EDB Postgres Advanced Server Guide* available at:
-
-[https://www.enterprisedb.com/docs](/epas/10/)
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](/epas/10/epas_guide/03_database_administration/06_unicode_collation_algorithm).
 
 ## Locales Requiring Product Keys
 

product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx

@@ -1068,8 +1068,8 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
- Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
-
+ Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres` and the name of the default database will be `postgres`. The few Advanced Server’s features compatible with Oracle databases will be available with this mode. However, we recommend using the Advanced server in redwood compatibility mode to use all its features.
+ 
 `--redwood-like`
 
  Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL-compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.

product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx

@@ -50,17 +50,15 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using the Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
 
 `--redwood-like`
 
-Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
 
 `--icu-short-form`
 
-Include the `--icu-short-form` keywords to create a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, please refer to the *EDB Postgres Advanced Server Guide* available at:
-
-[https://www.enterprisedb.com/docs](/epas/latest/)
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](/epas/11/epas_guide/03_database_administration/06_unicode_collation_algorithm).
 
 <div class="toctree" maxdepth="3">
 

product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx

@@ -1211,7 +1211,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres` and the name of the default database will be `postgres`. The few Advanced Server’s features compatible with Oracle databases will be available with this mode. However, we recommend using the Advanced server in redwood compatibility mode to use all its features.
 
 `--redwood-like`
 

product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx

@@ -50,17 +50,15 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using the Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
 
 `--redwood-like`
 
-Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
 
 `--icu-short-form`
 
-Include the `--icu-short-form` keywords to create a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, please refer to the *EDB Postgres Advanced Server Guide* available at:
-
-[https://www.enterprisedb.com/docs](/epas/latest/)
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](/epas/12/epas_guide/03_database_administration/06_unicode_collation_algorithm).
 
 <div class="toctree" maxdepth="3">
 

product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx

@@ -962,7 +962,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres` and the name of the default database will be `postgres`. The few Advanced Server’s features compatible with Oracle databases will be available with this mode. However, we recommend using the Advanced server in redwood compatibility mode to use all its features.
 
 `--redwood-like`
 

product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx

@@ -50,17 +50,15 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser will be `postgres`, the name of the default database will be `postgres`, and Advanced Server’s features compatible with Oracle databases will not be available to the cluster.
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using the Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
 
 `--redwood-like`
 
-Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
 
 `--icu-short-form`
 
-Include the `--icu-short-form` keywords to create a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, please refer to the *EDB Postgres Advanced Server Guide* available at:
-
-[https://www.enterprisedb.com/docs](/epas/latest/)
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](/epas/13/epas_guide/03_database_administration/06_unicode_collation_algorithm).
 
 <div class="toctree" maxdepth="3">
 

product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx

@@ -285,7 +285,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres`, the name of the default database is `postgres`, and EDB Postgres Advanced Server’s features compatible with Oracle databases aren't available to the cluster.
+Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. The few Advanced Server’s features compatible with Oracle databases will be available with this mode. However, we recommend using the Advanced server in redwood compatibility mode to use all its features.
 
 `--redwood-like`
 

product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx

@@ -54,15 +54,15 @@ In addition to the cluster configuration options documented in the PostgreSQL co
 
 `--no-redwood-compat`
 
-Include the `--no-redwood-compat` keywords to instruct the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres`, the name of the default database is `postgres`, and EDB Postgres Advanced Server’s features compatible with Oracle databases aren't available to the cluster.
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
 
 `--redwood-like`
 
-Include the `--redwood-like` keywords to instruct the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
 
 `--icu-short-form`
 
-Include the `--icu-short-form` keywords to create a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. 
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](/epas/14/epas_guide/03_database_administration/06_unicode_collation_algorithm).
 
 <div class="toctree" maxdepth="3">
 

product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx

@@ -22,4 +22,6 @@ The following is the series of steps that occur during the DDL change replicatio
 -   The in-memory table metadata definition is refreshed to reflect the DDL change. The user is informed of successful completion of the operation.
 -   If an error occurs during the prior steps, any changes up to that point are rolled back so that the publication table, replication triggers, and shadow table are reverted back to their original state prior to the start of this operation. If one or more databases goes down before completion of the operation, the publication is marked as dirty to avoid further replication events.
 
-The following section describes how to initiate DDL change replication using the xDB Replication Console.
+!!! Note
+   When you execute the alterDDL command, non-MDN nodes shouldn't have any CDC changes during that window for MMR setup. If there are any CDC changes, it may result in data loss and a break in replication. 
+!!!