From c8c83ad6cde2ff0bc71873c4026f259bd5261fac Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 17 Aug 2022 15:09:10 +0530 Subject: [PATCH 01/27] EPAS - Added content as per DF-285 for EPAS 10 to 14 versions --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- .../index.mdx | 2 +- .../03_using_a_package_manager_to_install_advanced_server.mdx | 4 ++-- .../index.mdx | 2 +- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- .../index.mdx | 2 +- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- .../index.mdx | 2 +- .../managing_an_advanced_server_installation.mdx | 2 +- .../index.mdx | 2 +- 10 files changed, 11 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 1945e641aa5..ee609f49e5d 100644 --- a/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`, 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` diff --git a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 3f2a794d8e4..43d6d55659a 100644 --- a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -47,7 +47,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`, 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` diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 5beb45c7159..65f444f8f91 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`, 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. diff --git a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index c82c6c4b9b0..389e5afcbdb 100644 --- a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`, 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` diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index a4e1b5026e8..f0c78db6eea 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`, 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` diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 63f588bc81b..4dd8de5a8c6 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`, 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` diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 7f05e1af9ba..210d336f6bb 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`, 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` diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 0c055942a68..6e1e007078d 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`, 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` diff --git a/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx index 4df97f78965..ad62b4594cd 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx +++ b/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`, 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` diff --git a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx index 504895fcf7f..b8befa86266 100644 --- a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx @@ -54,7 +54,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`, 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` From 5da30a85d7de65bb2c73ff99ea87725ba525b51b Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 22 Aug 2022 12:43:10 -0400 Subject: [PATCH 02/27] changes --- .../01_ddl_change_replication.mdx | 4 +++- .../01_ddl_change_replication.mdx | 6 +++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx b/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx index 213e22f55ce..9f74b521016 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx +++ b/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 usually don't have any CDC changes during the MMR setup. If there are any changes on the altered table in the non-MDN node, it can result in data loss and a break in replication. +!!! \ No newline at end of file diff --git a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx index 5342bd4c674..4943ee8d8e6 100644 --- a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx @@ -20,4 +20,8 @@ The following is the series of steps that occur during the DDL change replicatio - The DDL statement is executed against the target table. The replication triggers and shadow table are modified accordingly. If an error occurs, you're notified and the operation stops. If `ddlChangeTableLock` is set to `true`, the exclusive lock is released. - These two actions are repeated on the target table for each database in the replication system. - The in-memory table metadata definition is refreshed to reflect the DDL change. You're notified when the operation completes successfully. -- If an error occurs during these steps, any changes up to that point are rolled back so that the publication table, replication triggers, and shadow table revert to their original state prior to the start of this operation. If one or more databases goes down before the operation finishes, the publication is marked as dirty to avoid further replication events. \ No newline at end of file +- If an error occurs during these steps, any changes up to that point are rolled back so that the publication table, replication triggers, and shadow table revert to their original state prior to the start of this operation. If one or more databases goes down before the operation finishes, the publication is marked as dirty to avoid further replication events. + +!!! Note + When you execute the alterDDL command, non-MDN nodes usually don't have any CDC changes during the MMR setup. If there are any changes on the altered table in the non-MDN node, it can result in data loss and a break in replication. +!!! \ No newline at end of file From a242d2e6e43fb0349652933b8244e729bee17a70 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:33:33 +0530 Subject: [PATCH 03/27] Update 03_using_a_package_manager_to_install_advanced_server.mdx --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index ee609f49e5d..b2e593b5634 100644 --- a/product_docs/docs/epas/10/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`. 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. + 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` From 2583be02c15b355d9e60f4e19e04b3414ae52e31 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:34:10 +0530 Subject: [PATCH 04/27] Update index.mdx --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 43d6d55659a..16cdd6f71f3 100644 --- a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -47,7 +47,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`. 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. +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` From 4130133451dd42db6107a7ba9904ef43ed406bab Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:36:14 +0530 Subject: [PATCH 05/27] Update 03_using_a_package_manager_to_install_advanced_server.mdx --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 65f444f8f91..e791e240da3 100644 --- a/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/product_docs/docs/epas/11/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx @@ -1068,7 +1068,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`. 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. + 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` From 16a56abdfd7d62d871aa5259e676571366a96689 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:36:46 +0530 Subject: [PATCH 06/27] Update index.mdx --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 389e5afcbdb..f7cf899e6af 100644 --- a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`. 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. +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` From 0c17666111be6573cb56f5915d5db934bdcc6ddf Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:37:44 +0530 Subject: [PATCH 07/27] Update 03_using_a_package_manager_to_install_advanced_server.mdx --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index f0c78db6eea..39d260055a3 100644 --- a/product_docs/docs/epas/12/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`. 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. +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` From 5deabf017e65f826c3f3526701d1d0238859da61 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:38:19 +0530 Subject: [PATCH 08/27] Update index.mdx --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 4dd8de5a8c6..d45645c902b 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`. 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. +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` From 31d4d48d03597155b28a6dc4ab346bac28b2d990 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:39:40 +0530 Subject: [PATCH 09/27] Update 03_using_a_package_manager_to_install_advanced_server.mdx --- .../03_using_a_package_manager_to_install_advanced_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx b/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx index 210d336f6bb..d3bd2c9fde9 100644 --- a/product_docs/docs/epas/13/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server.mdx +++ b/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`. 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. +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` From a1a05d899f948fd6055c6d0b87502b13e481fdc3 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:40:00 +0530 Subject: [PATCH 10/27] Update index.mdx --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 6e1e007078d..5e817b6f60b 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,7 +50,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`. 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. +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` From 27bb1cd1dc65b7bf444c62a67ea540be3fd52e59 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:40:45 +0530 Subject: [PATCH 11/27] Update managing_an_advanced_server_installation.mdx --- .../managing_an_advanced_server_installation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx b/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx index ad62b4594cd..1942de04098 100644 --- a/product_docs/docs/epas/14/epas_inst_linux/managing_an_advanced_server_installation.mdx +++ b/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`. 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. +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` From 5f79327c6c1ad94f976cb4e70fabee83952bb108 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 23 Aug 2022 13:41:12 +0530 Subject: [PATCH 12/27] Update index.mdx --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx index b8befa86266..42068679ce2 100644 --- a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx @@ -54,7 +54,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`. 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. +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` From 392d957f64b72f90de780ba138f0786b78efb421 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 25 Aug 2022 17:56:23 +0530 Subject: [PATCH 13/27] Update product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx Co-authored-by: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> --- .../index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx index 42068679ce2..884bf67f3ad 100644 --- a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx @@ -54,7 +54,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` 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. +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`. 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` From fb34edec7ffc9d2eb10f161c3e5299c9804d830f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 25 Aug 2022 09:26:59 -0400 Subject: [PATCH 14/27] backport and cleaned up option descriptions --- .../index.mdx | 6 +++--- .../index.mdx | 6 +++--- .../index.mdx | 6 +++--- .../index.mdx | 6 +++--- .../index.mdx | 6 +++--- 5 files changed, 15 insertions(+), 15 deletions(-) diff --git a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 16cdd6f71f3..1da9e5e7d48 100644 --- a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -47,15 +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` 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. +`--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: +`--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, please refer to the *EDB Postgres Advanced Server Guide* available at: [https://www.enterprisedb.com/docs](/epas/10/) diff --git a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index f7cf899e6af..5178fa74c9c 100644 --- a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,15 +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` 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. +`--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: +`--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, please refer to the *EDB Postgres Advanced Server Guide* available at: [https://www.enterprisedb.com/docs](/epas/latest/) diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index d45645c902b..61903132880 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,15 +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` 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. +`--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: +`--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, please refer to the *EDB Postgres Advanced Server Guide* available at: [https://www.enterprisedb.com/docs](/epas/latest/) diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 5e817b6f60b..ccf1018f7b4 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -50,15 +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` 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. +`--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: +`--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, please refer to the *EDB Postgres Advanced Server Guide* available at: [https://www.enterprisedb.com/docs](/epas/latest/) diff --git a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx index 884bf67f3ad..09e7a8a9db4 100644 --- a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/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` 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. +`--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.
From 7318cce60cdf061371f22f205898b16a3c3c795f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 25 Aug 2022 13:42:17 -0400 Subject: [PATCH 15/27] removed circular link from v10-13 --- .../index.mdx | 4 +--- .../index.mdx | 4 +--- .../index.mdx | 4 +--- .../index.mdx | 4 +--- 4 files changed, 4 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 1da9e5e7d48..dbe396aed2b 100644 --- a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -55,9 +55,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--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, 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. ## Locales Requiring Product Keys diff --git a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 5178fa74c9c..cabbf1b2efb 100644 --- a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,9 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--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, 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.
diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 61903132880..b5c971d1765 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,9 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--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, 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.
diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index ccf1018f7b4..9eeb967e304 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,9 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--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, 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.
From 302009b5fe09405e2f317d6a9342a2ddd8612f33 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 25 Aug 2022 14:05:06 -0400 Subject: [PATCH 16/27] added replacement links --- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- .../index.mdx | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index dbe396aed2b..5bbc91528ff 100644 --- a/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/10/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -55,7 +55,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--icu-short-form` creates 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/10/epas_guide/03_database_administration/06_unicode_collation_algorithm). ## Locales Requiring Product Keys diff --git a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index cabbf1b2efb..222d93a156e 100644 --- a/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/11/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,7 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--icu-short-form` creates 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/11/epas_guide/03_database_administration/06_unicode_collation_algorithm).
diff --git a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index b5c971d1765..0b566951f13 100644 --- a/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/12/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,7 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--icu-short-form` creates 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/12/epas_guide/03_database_administration/06_unicode_collation_algorithm).
diff --git a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx index 9eeb967e304..654b809eafe 100644 --- a/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/13/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/index.mdx @@ -58,7 +58,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--icu-short-form` creates 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/13/epas_guide/03_database_administration/06_unicode_collation_algorithm).
diff --git a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx index 09e7a8a9db4..901b72813bf 100644 --- a/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx +++ b/product_docs/docs/epas/14/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/index.mdx @@ -62,7 +62,7 @@ In addition to the cluster configuration options documented in the PostgreSQL co `--icu-short-form` -`--icu-short-form` creates 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).
From bd43d73481732ef738c3388e62b3b88e8e0ca4f1 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 30 Aug 2022 14:32:46 -0700 Subject: [PATCH 17/27] Update index.mdx Change release date for 4.5 to be 8/30 instead of 8/31 --- product_docs/docs/efm/4/efm_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/efm_rel_notes/index.mdx b/product_docs/docs/efm/4/efm_rel_notes/index.mdx index 9cb78a1250c..cad42377fc6 100644 --- a/product_docs/docs/efm/4/efm_rel_notes/index.mdx +++ b/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| From aca315037d962a7c3cf0654ca48fe96994a57a71 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Tue, 30 Aug 2022 16:00:24 -0700 Subject: [PATCH 18/27] Update index.mdx Simplify overview page and move image down. --- product_docs/docs/pgd/4/index.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/pgd/4/index.mdx b/product_docs/docs/pgd/4/index.mdx index fc016b775e7..4c59853c851 100644 --- a/product_docs/docs/pgd/4/index.mdx +++ b/product_docs/docs/pgd/4/index.mdx @@ -25,10 +25,10 @@ navigation: EDB Postgres Distributed provides multi-master replication and data distribution with advanced conflict management, data-loss protection, and throughput up to 5X faster than native logical replication, and enables distributed PostgreSQL clusters with high availability up to five 9s. -![node diagram](images/nodes.png) - By default EDB Postgres Distributed uses asynchronous replication, applying changes on the peer nodes only after the local commit. Additional levels of synchronicity can be configured between different nodes, groups of nodes or all nodes by configuring -[CAMO](/pgd/latest/overview/bdr/camo), [Group Commit ](/pgd/latest/overview/bdr/group-commit), or -[eager all node replication](/pgd/latest/overview/bdr/eager) features. +[Group Commit ](/pgd/latest/overview/bdr/group-commit), [CAMO](/pgd/latest/overview/bdr/camo), or +[Eager](/pgd/latest/overview/bdr/eager) replication. + +![node diagram](images/nodes.png) From abba850f70f19e471d2ec9eb8296bae407830412 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Wed, 31 Aug 2022 05:44:55 -0400 Subject: [PATCH 19/27] Removed extra space --- product_docs/docs/pgd/4/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/4/index.mdx b/product_docs/docs/pgd/4/index.mdx index 4c59853c851..52144f48afe 100644 --- a/product_docs/docs/pgd/4/index.mdx +++ b/product_docs/docs/pgd/4/index.mdx @@ -28,7 +28,7 @@ EDB Postgres Distributed provides multi-master replication and data distribution By default EDB Postgres Distributed uses asynchronous replication, applying changes on the peer nodes only after the local commit. Additional levels of synchronicity can be configured between different nodes, groups of nodes or all nodes by configuring -[Group Commit ](/pgd/latest/overview/bdr/group-commit), [CAMO](/pgd/latest/overview/bdr/camo), or +[Group Commit](/pgd/latest/overview/bdr/group-commit), [CAMO](/pgd/latest/overview/bdr/camo), or [Eager](/pgd/latest/overview/bdr/eager) replication. ![node diagram](images/nodes.png) From a5d3b62795db9e33ad9c643e8a5e4c38042b1e32 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 31 Aug 2022 11:22:21 -0400 Subject: [PATCH 20/27] BigAnimal: maximizing disk size --- .../release/getting_started/creating_a_cluster/index.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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 90ec7863007..cf83dfe71bb 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 @@ -73,6 +73,9 @@ 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 Azure, select <tbd>> as your instance, and then <storage> as your storage to get a max disk size of 64 TB and 256,000 IOPS. + - To maximize your disk size for AWS, select Rb5 as your instance, and then io2 Block Express as your storage to get a max 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,7 +86,7 @@ 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. To maximize your disk size, select Rb5 as your instance, and then io2 Block Express as your storage to get a max disk size of 64 TB and 256,000 IOPS. !!!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. From c01466d40492f3e886a2f512748914c7da562269 Mon Sep 17 00:00:00 2001 From: kelpoole <44814688+kelpoole@users.noreply.github.com> Date: Wed, 31 Aug 2022 09:22:55 -0700 Subject: [PATCH 21/27] Update pgd_4.1.0_rel_notes.mdx fixed version of CLI from 4.1.0 to 1.0.0 --- product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx index a861e7f5eb4..56448b678ac 100644 --- a/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx +++ b/product_docs/docs/pgd/4/rel_notes/pgd_4.1.0_rel_notes.mdx @@ -7,7 +7,7 @@ EDB Postgres Distributed version 4.1.0 includes the following: | Component | Version | Type | Description | | ------------------------ | ------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| CLI | 4.1.0 | Feature | Ability to gather information such as the current state of replication, consensus, and nodes for an EDB Postgres Distributed cluster using new [command-line interface (CLI)](/pgd/latest/cli). | +| CLI | 1.0.0 | Feature | Ability to gather information such as the current state of replication, consensus, and nodes for an EDB Postgres Distributed cluster using new [command-line interface (CLI)](/pgd/latest/cli). | | BDR | 4.1.0 | Feature | Support [in-place major upgrades](/pgd/latest/upgrades/bdr_pg_upgrade/) of Postgres on a data node with a new command-line utility, bdr_pg_upgrade. This utility uses the standard pg_upgrade command, and reduces the time and network bandwidth needed to do major version upgrades of a EDB Postgres Distributed cluster. | | BDR | 4.1.0 | Feature | Enable the ability to configure a [replication lag threshold](/pgd/latest/overview/bdr/lag-control/). After the threshold is met, the transaction commits get throttled. This threshold allows limiting RPO without incurring the latency impact on every transaction that comes with synchronous replication. | | BDR | 4.1.0 | Feature | [Global sequences](/pgd/latest/overview/bdr/sequences/#bdr-global-sequences) are automatically configured based on data type replacing the need to set up custom sequence handling configuration on every node. The new SnowflakeID algorithm replaces Timeshard, which had limitations. | From 5bb28aa3ec9b6618915d1e50b1bd663f49c62ac9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 31 Aug 2022 12:25:39 -0400 Subject: [PATCH 22/27] removed Azure info because it is already covered --- .../release/getting_started/creating_a_cluster/index.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) 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 cf83dfe71bb..db810bab7b3 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 @@ -74,8 +74,7 @@ Prior to creating your cluster, make sure you have enough resources. Without eno - 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 Azure, select <tbd>> as your instance, and then <storage> as your storage to get a max disk size of 64 TB and 256,000 IOPS. - - To maximize your disk size for AWS, select Rb5 as your instance, and then io2 Block Express as your storage to get a max disk size of 64 TB and 256,000 IOPS. + 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. From a145f0f786f4eda6597e5861dfda72ddc30acdfe Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 31 Aug 2022 15:37:00 -0400 Subject: [PATCH 23/27] changes --- .../42.3.3.1/01_jdbc_rel_notes/index.mdx | 3 +++ .../jdbc_42.5.0.1_rel_notes.mdx | 17 +++++++++++++++++ 2 files changed, 20 insertions(+) create mode 100644 product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx index 3d5b3283d41..f6ada78767e 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx @@ -1,5 +1,7 @@ --- title: "Release notes" +navigation: +- jdbc_42.5.0.1_rel_notes --- The EDB JDBC connector documentation describes the latest version of EDB JDBC connector. @@ -8,6 +10,7 @@ These release notes describe what's new in each release. When a minor or patch r | Version | Release Date | | ---------------------------------------- | ------------ | +| [42.5.0.1](jdbc_42.5.0.1_rel_notes) | 2022 Sep 1 | | [42.3.3.1](08_jdbc_42.3.3.1_rel_notes) | 2022 Apr 20 | | [42.3.2.1](09_jdbc_42.3.2.1_rel_notes) | 2022 Feb 15 | | [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 2021 Nov 5 | diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx new file mode 100644 index 00000000000..20d8bab16be --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx @@ -0,0 +1,17 @@ +--- +title: "Version 42.5.0.1" + +--- + +The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database. + +New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.0.1 include: + +| Type | Description | +| -------------- | ------------------------------------------------------------------------------- | +| Upstream Merge | Merged with the upstream community driver version 42.5.0. See the community [JDBC documentation](https://jdbc.postgresql.org/documentation/changelog.html#version_42.5.0) for details. | +| Security Fix | CVE-2022-31197 - Fixes the SQL generated in PgResultSet.refresh() to escape column identifiers in order to prevent SQL injection. Previously, the column names for both key and data columns were copied as-is into the generated SQL. This allowed for a malicious table with column names that included a statment terminator to be parsed and executed as multiple separate commands. Also, this fix adds a new test class ResultSetRefreshTest to verify this change. | +| Change | Migrate build to Gradle. | + + + From ffe3521b5909d358c008ea5fe452c5ba4e1a9ba9 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 31 Aug 2022 16:12:52 -0400 Subject: [PATCH 24/27] copy edit --- .../42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx index 20d8bab16be..94f1f75805a 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx @@ -11,7 +11,7 @@ New features, enhancements, bug fixes, and other changes in the EDB JDBC Connect | -------------- | ------------------------------------------------------------------------------- | | Upstream Merge | Merged with the upstream community driver version 42.5.0. See the community [JDBC documentation](https://jdbc.postgresql.org/documentation/changelog.html#version_42.5.0) for details. | | Security Fix | CVE-2022-31197 - Fixes the SQL generated in PgResultSet.refresh() to escape column identifiers in order to prevent SQL injection. Previously, the column names for both key and data columns were copied as-is into the generated SQL. This allowed for a malicious table with column names that included a statment terminator to be parsed and executed as multiple separate commands. Also, this fix adds a new test class ResultSetRefreshTest to verify this change. | -| Change | Migrate build to Gradle. | +| Change | Migrated build to Gradle. | From ac98c75bbb901ebf7ffb6947205040412158c5f6 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 1 Sep 2022 09:59:06 +0530 Subject: [PATCH 25/27] Added the version 42.5.0.1 and edited requirements.mdx file --- .../01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx | 0 .../01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx | 0 .../01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx | 0 .../{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/index.mdx | 0 .../01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx | 0 .../{42.3.3.1 => 42.5.0.1}/02_requirements_overview.mdx | 1 + .../03_advanced_server_jdbc_connector_overview.mdx | 0 .../ibm_power_ppc64le/index.mdx | 0 .../ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx | 0 .../ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx | 0 .../ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx | 0 .../01_installing_the_connector_with_an_rpm_package/index.mdx | 0 .../x86_amd64/index.mdx | 0 .../x86_amd64/jdbc42_centos7_x86.mdx | 0 .../x86_amd64/jdbc42_deb10_x86.mdx | 0 .../x86_amd64/jdbc42_other_linux8_x86.mdx | 0 .../x86_amd64/jdbc42_rhel7_x86.mdx | 0 .../x86_amd64/jdbc42_rhel8_x86.mdx | 0 .../x86_amd64/jdbc42_sles12_x86.mdx | 0 .../x86_amd64/jdbc42_sles15_x86.mdx | 0 .../x86_amd64/jdbc42_ubuntu18_x86.mdx | 0 .../x86_amd64/jdbc42_ubuntu20_x86.mdx | 0 ...04_using_the_graphical_installer_to_install_the_connector.mdx | 0 .../05_configuring_the_advanced_server_jdbc_connector.mdx | 0 .../13_upgrading_rpm_install.mdx | 0 .../04_installing_and_configuring_the_jdbc_connector/index.mdx | 0 .../01_loading_the_advanced_server_jdbc_connector.mdx | 0 .../01_additional_connection_properties.mdx | 0 .../02_preferring_synchronous_secondary_database_servers.mdx | 0 .../02_connecting_to_the_database/index.mdx | 0 .../03_executing_sql_statements_through_statement_objects.mdx | 0 .../04_retrieving_results_from_a_resultset_object.mdx | 0 .../05_freeing_resources.mdx | 0 .../06_handling_errors.mdx | 0 .../index.mdx | 0 .../{42.3.3.1 => 42.5.0.1}/05a_using_advanced_queueing.mdx | 0 .../06_executing_sql_commands_with_executeUpdate().mdx | 0 .../07_adding_a_graphical_interface_to_a_java_program.mdx | 0 .../01_reducing_client-side_resource_requirements.mdx | 0 .../02_using_preparedstatements_to_send_sql_commands.mdx | 0 .../03_executing_stored_procedures.mdx | 0 .../04_using_ref_cursors_with_java.mdx | 0 .../05_using_bytea_data_with_java.mdx | 0 .../06_using_object_types_and_collections_with_java.mdx | 0 ...07_asynchronous_notification_handling_with_noticelistener.mdx | 0 .../08_advanced_jdbc_connector_functionality/index.mdx | 0 .../01_using_ssl/01_configuring_the_server.mdx | 0 .../01_using_ssl/02_configuring_the_client.mdx | 0 .../01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx | 0 .../04_using_certificate_authentication_without_a_password.mdx | 0 .../09_security_and_encryption/01_using_ssl/index.mdx | 0 .../09_security_and_encryption/02_scram_compatibility.mdx | 0 .../03_support_for_gssapi_encrypted_connection.mdx | 0 .../{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/index.mdx | 0 .../10_advanced_server_jdbc_connector_logging.mdx | 0 .../{42.3.3.1 => 42.5.0.1}/11_reference_jdbc_data_types.mdx | 0 .../images/core_classes_and_interfaces.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/drivermanager_drivers.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/jdbc_class_relationships.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_complete.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_dialog.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_wizard.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/ready_to_install.png | 0 .../images/selecting_the_connectors_installer.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/starting_stackbuilder_plus.png | 0 .../{42.3.3.1 => 42.5.0.1}/images/the_showemployees_window.png | 0 .../docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/index.mdx | 0 71 files changed, 1 insertion(+) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/02_requirements_overview.mdx (94%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/03_advanced_server_jdbc_connector_overview.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/04_installing_and_configuring_the_jdbc_connector/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/05a_using_advanced_queueing.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/06_executing_sql_commands_with_executeUpdate().mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/07_adding_a_graphical_interface_to_a_java_program.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/08_advanced_jdbc_connector_functionality/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/01_using_ssl/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/02_scram_compatibility.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/09_security_and_encryption/index.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/10_advanced_server_jdbc_connector_logging.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/11_reference_jdbc_data_types.mdx (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/core_classes_and_interfaces.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/drivermanager_drivers.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/jdbc_class_relationships.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_complete.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_dialog.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/jdbc_installation_wizard.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/ready_to_install.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/selecting_the_connectors_installer.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/starting_stackbuilder_plus.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/images/the_showemployees_window.png (100%) rename product_docs/docs/jdbc_connector/{42.3.3.1 => 42.5.0.1}/index.mdx (100%) diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/02_requirements_overview.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/02_requirements_overview.mdx similarity index 94% rename from product_docs/docs/jdbc_connector/42.3.3.1/02_requirements_overview.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/02_requirements_overview.mdx index c15528367ee..2533248f155 100644 --- a/product_docs/docs/jdbc_connector/42.3.3.1/02_requirements_overview.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/02_requirements_overview.mdx @@ -15,6 +15,7 @@ This table lists the latest JDBC Connector versions and their supported correspo | JDBC Connector | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | EPAS 10 | | -------------------------------------------------------------- | ------- | ------- | ------- | ------- | ------- | +| [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx) | Y | Y | Y | Y | Y | | [42.3.3.1](01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx) | Y | Y | Y | Y | Y | | [42.3.2.1](01_jdbc_rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx) | Y | Y | Y | Y | Y | | [42.2.24.1](01_jdbc_rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx) | Y | Y | Y | Y | Y | diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/03_advanced_server_jdbc_connector_overview.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/03_advanced_server_jdbc_connector_overview.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/03_advanced_server_jdbc_connector_overview.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/03_advanced_server_jdbc_connector_overview.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_rhel8_ppcle.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles12_ppcle.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/ibm_power_ppc64le/jdbc42_sles15_ppcle.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_centos7_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_deb10_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_other_linux8_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel7_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_rhel8_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles12_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_sles15_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu18_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/x86_amd64/jdbc42_ubuntu20_x86.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/04_using_the_graphical_installer_to_install_the_connector.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/05_configuring_the_advanced_server_jdbc_connector.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/13_upgrading_rpm_install.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/04_installing_and_configuring_the_jdbc_connector/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/04_installing_and_configuring_the_jdbc_connector/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/01_loading_the_advanced_server_jdbc_connector.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/02_preferring_synchronous_secondary_database_servers.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/03_executing_sql_statements_through_statement_objects.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/04_retrieving_results_from_a_resultset_object.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/05_freeing_resources.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/06_handling_errors.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/05a_using_advanced_queueing.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05a_using_advanced_queueing.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/05a_using_advanced_queueing.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/05a_using_advanced_queueing.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/06_executing_sql_commands_with_executeUpdate().mdx b/product_docs/docs/jdbc_connector/42.5.0.1/06_executing_sql_commands_with_executeUpdate().mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/06_executing_sql_commands_with_executeUpdate().mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/06_executing_sql_commands_with_executeUpdate().mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/07_adding_a_graphical_interface_to_a_java_program.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/07_adding_a_graphical_interface_to_a_java_program.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/07_adding_a_graphical_interface_to_a_java_program.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/07_adding_a_graphical_interface_to_a_java_program.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/01_reducing_client-side_resource_requirements.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/02_using_preparedstatements_to_send_sql_commands.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/03_executing_stored_procedures.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/04_using_ref_cursors_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/05_using_bytea_data_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/06_using_object_types_and_collections_with_java.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/07_asynchronous_notification_handling_with_noticelistener.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/08_advanced_jdbc_connector_functionality/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/08_advanced_jdbc_connector_functionality/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/01_configuring_the_server.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/02_configuring_the_client.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/03_testing_the_ssl_jdbc_connection.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/04_using_certificate_authentication_without_a_password.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/01_using_ssl/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/01_using_ssl/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/02_scram_compatibility.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/02_scram_compatibility.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/02_scram_compatibility.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/02_scram_compatibility.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/03_support_for_gssapi_encrypted_connection.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/09_security_and_encryption/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/09_security_and_encryption/index.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/10_advanced_server_jdbc_connector_logging.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/10_advanced_server_jdbc_connector_logging.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/10_advanced_server_jdbc_connector_logging.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/10_advanced_server_jdbc_connector_logging.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/11_reference_jdbc_data_types.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/11_reference_jdbc_data_types.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/11_reference_jdbc_data_types.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/11_reference_jdbc_data_types.mdx diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/core_classes_and_interfaces.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/core_classes_and_interfaces.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/core_classes_and_interfaces.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/core_classes_and_interfaces.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/drivermanager_drivers.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/drivermanager_drivers.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/drivermanager_drivers.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/drivermanager_drivers.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_class_relationships.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_class_relationships.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_class_relationships.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_class_relationships.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_complete.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_complete.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_complete.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_complete.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_dialog.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_dialog.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_dialog.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_dialog.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_wizard.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_wizard.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/jdbc_installation_wizard.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/jdbc_installation_wizard.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/ready_to_install.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/ready_to_install.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/ready_to_install.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/ready_to_install.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/selecting_the_connectors_installer.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/selecting_the_connectors_installer.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/selecting_the_connectors_installer.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/starting_stackbuilder_plus.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/starting_stackbuilder_plus.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/starting_stackbuilder_plus.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/starting_stackbuilder_plus.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/images/the_showemployees_window.png b/product_docs/docs/jdbc_connector/42.5.0.1/images/the_showemployees_window.png similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/images/the_showemployees_window.png rename to product_docs/docs/jdbc_connector/42.5.0.1/images/the_showemployees_window.png diff --git a/product_docs/docs/jdbc_connector/42.3.3.1/index.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/index.mdx similarity index 100% rename from product_docs/docs/jdbc_connector/42.3.3.1/index.mdx rename to product_docs/docs/jdbc_connector/42.5.0.1/index.mdx From ceafe3de36fe9b64c66112ac3d7c438331fd3476 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 1 Sep 2022 08:19:20 -0400 Subject: [PATCH 26/27] revision --- .../08_replicating_ddl_changes/01_ddl_change_replication.mdx | 2 +- .../08_replicating_ddl_changes/01_ddl_change_replication.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx b/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx index 9f74b521016..7c4f8c52ff8 100644 --- a/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx +++ b/product_docs/docs/eprs/6.2/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx @@ -23,5 +23,5 @@ The following is the series of steps that occur during the DDL change replicatio - 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. !!! Note - When you execute the alterDDL command, non-MDN nodes usually don't have any CDC changes during the MMR setup. If there are any changes on the altered table in the non-MDN node, it can result in data loss and a break in replication. + 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. !!! \ No newline at end of file diff --git a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx index 4943ee8d8e6..b2f25d346bc 100644 --- a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx @@ -23,5 +23,5 @@ The following is the series of steps that occur during the DDL change replicatio - If an error occurs during these steps, any changes up to that point are rolled back so that the publication table, replication triggers, and shadow table revert to their original state prior to the start of this operation. If one or more databases goes down before the operation finishes, the publication is marked as dirty to avoid further replication events. !!! Note - When you execute the alterDDL command, non-MDN nodes usually don't have any CDC changes during the MMR setup. If there are any changes on the altered table in the non-MDN node, it can result in data loss and a break in replication. + 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. !!! \ No newline at end of file From f5775cfc212b5b2a4dbbfe05378caf4c2021e071 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 1 Sep 2022 08:50:08 -0400 Subject: [PATCH 27/27] Removed replicated tip and fixed list formatting --- .../release/getting_started/creating_a_cluster/index.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) 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 db810bab7b3..bed0a1a9ef3 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 @@ -85,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. To maximize your disk size, select Rb5 as your instance, and then io2 Block Express as your storage to get a max disk size of 64 TB and 256,000 IOPS. + - 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.