From 6338233fe88ba31ac7eff310e1c4453f654980a1 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 16 Mar 2022 16:15:29 -0400 Subject: [PATCH 1/2] Hadoop FDW - version consolidation --- .../2.7.0/02_requirements_overview.mdx | 44 ---------------- ...12_uninstalling_the_mysql_data_adapter.mdx | 31 ----------- .../2/02_requirements_overview.mdx | 52 +++++++++++++++++++ .../{2.7.0 => 2}/03_architecture_overview.mdx | 0 .../01_mysql_rhel8_x86.mdx | 0 .../02_mysql_other_linux8_x86.mdx | 0 .../03_mysql_rhel7_x86.mdx | 0 .../04_mysql_centos7_x86.mdx | 0 .../05_mysql_sles15_x86.mdx | 0 .../07_mysql_sles12_x86.mdx | 0 .../09_mysql_ubuntu20_deb10_x86.mdx | 0 .../11_mysql_ubuntu18_deb9_x86.mdx | 0 .../13_mysql_rhel8_ppcle.mdx | 0 .../15_mysql_rhel7_ppcle.mdx | 0 .../17_mysql_sles15_ppcle.mdx | 0 .../19_mysql_sles12_ppcle.mdx | 0 .../index.mdx | 0 .../05_updating_the_mysql_data_adapter.mdx | 0 .../{2.7.0 => 2}/06_features_of_mysql_fdw.mdx | 0 .../07_configuring_the_mysql_data_adapter.mdx | 0 ...8_example_using_the_mysql_data_adapter.mdx | 0 .../09_example_import_foreign_schema.mdx | 0 .../10_example_join_push_down.mdx | 0 .../10a_example_aggregate_func_push_down.mdx | 0 .../11_identifying_data_adapter_version.mdx | 0 ...12_uninstalling_the_mysql_data_adapter.mdx | 36 +++++++++++++ .../{2.7.0 => 2}/13_troubleshooting.mdx | 0 .../{2.7.0 => 2}/images/EDB_logo.png | 0 .../ambari_administrative_interface.png | 0 .../{2.7.0 => 2}/images/edb_logo.svg | 0 .../images/mysql_server_with_postgres.png | 0 .../progress_as_the_servers_restart.png | 0 .../images/restart_the_server.png | 0 .../images/setup_wizard_ready.png | 0 .../specify_an_installation_directory.png | 0 ...the_installation_wizard_welcome_screen.png | 0 .../mysql_data_adapter/{2.7.0 => 2}/index.mdx | 4 +- .../2/mysql_rel_notes/index.mdx | 21 ++++++++ .../mysql_rel_notes/mysql2.5.1_rel_notes.mdx | 12 +++++ .../mysql_rel_notes/mysql2.5.3_rel_notes.mdx | 14 +++++ .../mysql_rel_notes/mysql2.5.5_rel_notes.mdx | 15 ++++++ .../mysql_rel_notes/mysql2.6.0_rel_notes.mdx | 14 +++++ .../mysql_rel_notes/mysql2.7.0_rel_notes.mdx} | 5 +- static/_redirects | 6 ++- 44 files changed, 176 insertions(+), 78 deletions(-) delete mode 100644 product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/02_requirements_overview.mdx rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/03_architecture_overview.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/01_mysql_rhel8_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/02_mysql_other_linux8_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/03_mysql_rhel7_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/04_mysql_centos7_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/05_mysql_sles15_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/07_mysql_sles12_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/09_mysql_ubuntu20_deb10_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/11_mysql_ubuntu18_deb9_x86.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/13_mysql_rhel8_ppcle.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/15_mysql_rhel7_ppcle.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/17_mysql_sles15_ppcle.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/19_mysql_sles12_ppcle.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/04_installing_the_mysql_data_adapter/index.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/05_updating_the_mysql_data_adapter.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/06_features_of_mysql_fdw.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/07_configuring_the_mysql_data_adapter.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/08_example_using_the_mysql_data_adapter.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/09_example_import_foreign_schema.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/10_example_join_push_down.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/10a_example_aggregate_func_push_down.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/11_identifying_data_adapter_version.mdx (100%) create mode 100644 product_docs/docs/mysql_data_adapter/2/12_uninstalling_the_mysql_data_adapter.mdx rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/13_troubleshooting.mdx (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/EDB_logo.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/ambari_administrative_interface.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/edb_logo.svg (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/mysql_server_with_postgres.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/progress_as_the_servers_restart.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/restart_the_server.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/setup_wizard_ready.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/specify_an_installation_directory.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/images/the_installation_wizard_welcome_screen.png (100%) rename product_docs/docs/mysql_data_adapter/{2.7.0 => 2}/index.mdx (93%) create mode 100644 product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx rename product_docs/docs/mysql_data_adapter/{2.7.0/01_rel_notes.mdx => 2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx} (86%) diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx deleted file mode 100644 index 5e97ed79a31..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.7.0/02_requirements_overview.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: "Requirements Overview" ---- - -## Supported Versions - -The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 10 and above. - -## Supported Platforms - -### The MySQL Foreign Data Wrapper is supported for MySQL 8 on the following platforms: - -**Linux x86-64** - - - RHEL 8/OL 8 - - Rocky Linux 8/AlmaLinux 8 - - RHEL 7/OL 7 - - CentOS 7 - - SLES 15 - - SLES 12 - - Ubuntu 20.04/18.04 LTS - - Debian 10.x/9.x - -**Linux on IBM Power (ppc64le)** - -- RHEL 8 -- SLES 15 -- SLES 12 - - -### The MySQL Foreign Data Wrapper is supported for MySQL 5 on the following platforms: - -**Linux x86-64** - - - RHEL 7/OL 7 - - CentOS 7 - - SLES 12 - - Ubuntu 18.04 LTS - - Debian 9.x - - -**Linux on IBM Power (ppc64le)** - -- RHEL 7 diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx deleted file mode 100644 index a290dbfea07..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.7.0/12_uninstalling_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Uninstalling the MySQL Foreign Data Wrapper" ---- - - - -**Uninstalling an RPM Package** - -You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command: - -- On RHEL or CentOS 7: - - `yum remove edb-as-mysql_fdw` - -Where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to uninstall MySQL 5.0 on RHEL 7: - - `yum remove edb-as-mysql5_fdw` - -- On RHEL or Rocky Linux or AlmaLinux 8: - - `dnf remove edb-as-mysql8_fdw` - -Where `xx` is the server version number. - -**Uninstalling MySQL Foreign Data Wrapper on a Debian or Ubuntu Host** - -- To uninstall MySQL Foreign Data Wrapper on a Debian or Ubuntu host, invoke the following command: - - `apt-get remove edb-as-mysql-fdw` - -Where `xx` is the server version number. diff --git a/product_docs/docs/mysql_data_adapter/2/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2/02_requirements_overview.mdx new file mode 100644 index 00000000000..c918e1b8868 --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/02_requirements_overview.mdx @@ -0,0 +1,52 @@ +--- +title: "Supported Database and MySQL Versions" +--- + +## Supported Database Versions + +This table lists the latest MySQL Foreign Data Wrapper versions and their supported corresponding EDB Postgres Advanced Server (EPAS) versions. MySQL Foreign Data Wrapper is supported on the same platforms as EDB Postgres Advanced Server. See [Product Compatibility](https://www.enterprisedb.com/platform-compatibility#epas) for details. + +| MySQL Foreign Data Wrapper | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 | EPAS 10 | +| -------------------------- | ------- | ------- | ------- | ------- | ------- | +| 2.7.0 | Y | Y | Y | Y | Y | +| 2.6.0 | N | Y | Y | Y | Y | +| 2.5.5 | N | Y | N | N | N | +| 2.5.3 | N | N | Y | N | N | +| 2.5.1 | N | N | N | Y | N | + +## Supported MySQL Versions + +### The MySQL Foreign Data Wrapper is supported for MySQL 8 on the following platforms: + +**Linux x86-64** + + - RHEL 8/OL 8 + - Rocky Linux 8/AlmaLinux 8 + - RHEL 7/OL 7 + - CentOS 7 + - SLES 15 + - SLES 12 + - Ubuntu 20.04/18.04 LTS + - Debian 10.x/9.x + +**Linux on IBM Power (ppc64le)** + +- RHEL 8 +- SLES 15 +- SLES 12 + + +### The MySQL Foreign Data Wrapper is supported for MySQL 5 on the following platforms: + +**Linux x86-64** + + - RHEL 7/OL 7 + - CentOS 7 + - SLES 12 + - Ubuntu 18.04 LTS + - Debian 9.x + + +**Linux on IBM Power (ppc64le)** + +- RHEL 7 diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/03_architecture_overview.mdx b/product_docs/docs/mysql_data_adapter/2/03_architecture_overview.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/03_architecture_overview.mdx rename to product_docs/docs/mysql_data_adapter/2/03_architecture_overview.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/01_mysql_rhel8_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/01_mysql_rhel8_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/01_mysql_rhel8_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/01_mysql_rhel8_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/02_mysql_other_linux8_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/02_mysql_other_linux8_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/02_mysql_other_linux8_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/02_mysql_other_linux8_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/03_mysql_rhel7_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/03_mysql_rhel7_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/03_mysql_rhel7_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/03_mysql_rhel7_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/04_mysql_centos7_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/04_mysql_centos7_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/04_mysql_centos7_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/04_mysql_centos7_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/05_mysql_sles15_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/05_mysql_sles15_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/05_mysql_sles15_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/05_mysql_sles15_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/07_mysql_sles12_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/07_mysql_sles12_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/07_mysql_sles12_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/07_mysql_sles12_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/09_mysql_ubuntu20_deb10_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/09_mysql_ubuntu20_deb10_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/09_mysql_ubuntu20_deb10_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/09_mysql_ubuntu20_deb10_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/11_mysql_ubuntu18_deb9_x86.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/11_mysql_ubuntu18_deb9_x86.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/11_mysql_ubuntu18_deb9_x86.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/11_mysql_ubuntu18_deb9_x86.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/13_mysql_rhel8_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/13_mysql_rhel8_ppcle.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/13_mysql_rhel8_ppcle.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/13_mysql_rhel8_ppcle.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/15_mysql_rhel7_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/15_mysql_rhel7_ppcle.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/15_mysql_rhel7_ppcle.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/15_mysql_rhel7_ppcle.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/17_mysql_sles15_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/17_mysql_sles15_ppcle.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/17_mysql_sles15_ppcle.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/17_mysql_sles15_ppcle.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/19_mysql_sles12_ppcle.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/19_mysql_sles12_ppcle.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/19_mysql_sles12_ppcle.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/19_mysql_sles12_ppcle.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/index.mdx b/product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/index.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/04_installing_the_mysql_data_adapter/index.mdx rename to product_docs/docs/mysql_data_adapter/2/04_installing_the_mysql_data_adapter/index.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2/05_updating_the_mysql_data_adapter.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/05_updating_the_mysql_data_adapter.mdx rename to product_docs/docs/mysql_data_adapter/2/05_updating_the_mysql_data_adapter.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/06_features_of_mysql_fdw.mdx b/product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/06_features_of_mysql_fdw.mdx rename to product_docs/docs/mysql_data_adapter/2/06_features_of_mysql_fdw.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/07_configuring_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2/07_configuring_the_mysql_data_adapter.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/07_configuring_the_mysql_data_adapter.mdx rename to product_docs/docs/mysql_data_adapter/2/07_configuring_the_mysql_data_adapter.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/08_example_using_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2/08_example_using_the_mysql_data_adapter.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/08_example_using_the_mysql_data_adapter.mdx rename to product_docs/docs/mysql_data_adapter/2/08_example_using_the_mysql_data_adapter.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/09_example_import_foreign_schema.mdx b/product_docs/docs/mysql_data_adapter/2/09_example_import_foreign_schema.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/09_example_import_foreign_schema.mdx rename to product_docs/docs/mysql_data_adapter/2/09_example_import_foreign_schema.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/10_example_join_push_down.mdx b/product_docs/docs/mysql_data_adapter/2/10_example_join_push_down.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/10_example_join_push_down.mdx rename to product_docs/docs/mysql_data_adapter/2/10_example_join_push_down.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/10a_example_aggregate_func_push_down.mdx b/product_docs/docs/mysql_data_adapter/2/10a_example_aggregate_func_push_down.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/10a_example_aggregate_func_push_down.mdx rename to product_docs/docs/mysql_data_adapter/2/10a_example_aggregate_func_push_down.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/11_identifying_data_adapter_version.mdx b/product_docs/docs/mysql_data_adapter/2/11_identifying_data_adapter_version.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/11_identifying_data_adapter_version.mdx rename to product_docs/docs/mysql_data_adapter/2/11_identifying_data_adapter_version.mdx diff --git a/product_docs/docs/mysql_data_adapter/2/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2/12_uninstalling_the_mysql_data_adapter.mdx new file mode 100644 index 00000000000..350212dd5ac --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/12_uninstalling_the_mysql_data_adapter.mdx @@ -0,0 +1,36 @@ +--- +title: "Uninstalling the MySQL Foreign Data Wrapper" +--- + + + +You can use the `remove` command to uninstall MongoDB Foreign Data Wrapper packages. To uninstall, open a terminal window, assume superuser privileges, and enter the command applicable to the operating system and package manager used for the installation: + +- On RHEL or CentOS 7: + + `yum remove edb-as-mysql_fdw` + + Where: + - `xx` is the EDB Postgres Advanced Server version. + - `x` is the supported release version number of MySQL. +- On RHEL or Rocky Linux or AlmaLinux 8: + + `dnf remove edb-as-mysql8_fdw` + + Where `` is the EDB Postgres Advanced Server version. +- On SLES: + + `zypper remove edb-as-mysql_fdw` + + Where: + - `xx` is the EDB Postgres Advanced Server version. + - `x` is the supported release version number of MySQL. +- On Debian or Ubuntu + + `apt-get remove edb-as-mysql-fdw` + + Where `` is the EDB Postgres Advanced Server version. + + + + diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/13_troubleshooting.mdx b/product_docs/docs/mysql_data_adapter/2/13_troubleshooting.mdx similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/13_troubleshooting.mdx rename to product_docs/docs/mysql_data_adapter/2/13_troubleshooting.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/EDB_logo.png b/product_docs/docs/mysql_data_adapter/2/images/EDB_logo.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/EDB_logo.png rename to product_docs/docs/mysql_data_adapter/2/images/EDB_logo.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/ambari_administrative_interface.png b/product_docs/docs/mysql_data_adapter/2/images/ambari_administrative_interface.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/ambari_administrative_interface.png rename to product_docs/docs/mysql_data_adapter/2/images/ambari_administrative_interface.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/edb_logo.svg b/product_docs/docs/mysql_data_adapter/2/images/edb_logo.svg similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/edb_logo.svg rename to product_docs/docs/mysql_data_adapter/2/images/edb_logo.svg diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/mysql_server_with_postgres.png b/product_docs/docs/mysql_data_adapter/2/images/mysql_server_with_postgres.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/mysql_server_with_postgres.png rename to product_docs/docs/mysql_data_adapter/2/images/mysql_server_with_postgres.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/progress_as_the_servers_restart.png b/product_docs/docs/mysql_data_adapter/2/images/progress_as_the_servers_restart.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/progress_as_the_servers_restart.png rename to product_docs/docs/mysql_data_adapter/2/images/progress_as_the_servers_restart.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/restart_the_server.png b/product_docs/docs/mysql_data_adapter/2/images/restart_the_server.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/restart_the_server.png rename to product_docs/docs/mysql_data_adapter/2/images/restart_the_server.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/setup_wizard_ready.png b/product_docs/docs/mysql_data_adapter/2/images/setup_wizard_ready.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/setup_wizard_ready.png rename to product_docs/docs/mysql_data_adapter/2/images/setup_wizard_ready.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/specify_an_installation_directory.png b/product_docs/docs/mysql_data_adapter/2/images/specify_an_installation_directory.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/specify_an_installation_directory.png rename to product_docs/docs/mysql_data_adapter/2/images/specify_an_installation_directory.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/images/the_installation_wizard_welcome_screen.png b/product_docs/docs/mysql_data_adapter/2/images/the_installation_wizard_welcome_screen.png similarity index 100% rename from product_docs/docs/mysql_data_adapter/2.7.0/images/the_installation_wizard_welcome_screen.png rename to product_docs/docs/mysql_data_adapter/2/images/the_installation_wizard_welcome_screen.png diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/index.mdx b/product_docs/docs/mysql_data_adapter/2/index.mdx similarity index 93% rename from product_docs/docs/mysql_data_adapter/2.7.0/index.mdx rename to product_docs/docs/mysql_data_adapter/2/index.mdx index d882c59bbe2..523d4b7095a 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/index.mdx @@ -1,5 +1,7 @@ --- -title: "MySQL Foreign Data Wrapper Guide" +title: "MySQL Foreign Data Wrapper" +navigation: +- mysql_rel_notes --- The MySQL Foreign Data Wrapper (`mysql_fdw`) is a Postgres extension that allows you to access data that resides on a MySQL database from EDB Postgres Advanced Server. It is a writable foreign data wrapper that you can use with Postgres functions and utilities, or in conjunction with other data that resides on a Postgres host. diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx new file mode 100644 index 00000000000..8f33cef04f6 --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/index.mdx @@ -0,0 +1,21 @@ +--- +title: "Release notes" +redirects: + - ../01_whats_new/ +navigation: +- mysql2.7.0_rel_notes +- mysql2.6.0_rel_notes +- mysql2.5.5_rel_notes +- mysql2.5.3_rel_notes +- mysql2.5.1_rel_notes +--- + +The MySQL Foreign Data Wrapper documentation describes the latest version of MySQL Foreign Data Wrapper 5 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators within the content about what release introduced the feature. + +| Version | Release Date | +| ----------------------------- | ------------ | +| [2.7.0](mysql2.7.0_rel_notes) | 2021 Dec 02 | +| [2.6.0](mysql2.6.0_rel_notes) | 2021 May 18 | +| [2.5.5](mysql2.5.5_rel_notes) | 2020 Nov 23 | +| [2.5.3](mysql2.5.3_rel_notes) | 2019 Dec 10 | +| [2.5.1](mysql2.5.1_rel_notes) | 2018 Nov 28 | \ No newline at end of file diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx new file mode 100644 index 00000000000..f8d483f405a --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.1_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: "Version 2.5.1" +--- + + +Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.1 include: + +| Type | Description | +| ---- |------------ | +| Enhancement | Support for EDB Postgres Advanced Server 11. | + + diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx new file mode 100644 index 00000000000..7cea0df5ecc --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.3_rel_notes.mdx @@ -0,0 +1,14 @@ +--- +title: "Version 2.5.3" +redirect: +- 01_rel_notes +--- + + +Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.3 include: + +| Type | Description | +| ---- |------------ | +| Enhancement | Support for EDB Postgres Advanced Server 12. | + + diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx new file mode 100644 index 00000000000..09316594155 --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.5.5_rel_notes.mdx @@ -0,0 +1,15 @@ +--- +title: "Version 2.5.5" +redirect: +- 01_rel_notes +--- + + +Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.5.5 include: + +| Type | Description | +| ----------- |------------ | +| Enhancement | Support for EDB Postgres Advanced Server 13. | +| Enhancement | Support for Ubuntu 20.04 LTS platform. | + + diff --git a/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx new file mode 100644 index 00000000000..05a452514a6 --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.6.0_rel_notes.mdx @@ -0,0 +1,14 @@ +--- +title: "Version 2.6.0" +redirect: +--- + + +Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.6.0 include: + +| Type | Description | +| ---- |------------ | +| Feature | Support for push down joins to the remote MySQL servers. | +| Enhancement | Support for EDB Postgres Advanced Server 13. | +| Enhancement | Support for Ubuntu 20.04 LTS platform. | + diff --git a/product_docs/docs/mysql_data_adapter/2.7.0/01_rel_notes.mdx b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx similarity index 86% rename from product_docs/docs/mysql_data_adapter/2.7.0/01_rel_notes.mdx rename to product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx index 2a26d2cc553..6bd8a54b52e 100644 --- a/product_docs/docs/mysql_data_adapter/2.7.0/01_rel_notes.mdx +++ b/product_docs/docs/mysql_data_adapter/2/mysql_rel_notes/mysql2.7.0_rel_notes.mdx @@ -1,5 +1,7 @@ --- -title: "Release Notes" +title: "Version 2.7.0" +redirect: +- 01_rel_notes --- @@ -7,6 +9,7 @@ Enhancements, bug fixes, and other changes in MySQL Foreign Data Wrapper 2.7.0 i | Type | Description | | ---- |------------ | +| Enhancement | Support for EDB Postgres Advanced Server 14. | | Enhancement | MySQL Foreign Data Wrapper now supports min, max, sum, avg, and count aggregate function pushdown. You can now push aggregates to the remote MySQL server instead of fetching all of the rows and aggregating them locally. This improves performance for the cases where aggregates can be pushed down. Aggregate filters and orders are not pushed down as MySQL does not support them. | | Bug Fix | Function expression deparsing implicit/explicit coercion sending wrong query to the MySQL server. | | Bug Fix | Import foreign schema failure due to SET type. | diff --git a/static/_redirects b/static/_redirects index 88780c5f7a2..491f6381dbb 100644 --- a/static/_redirects +++ b/static/_redirects @@ -120,13 +120,17 @@ /docs/migration_portal/3.5.0/* /docs/migration_portal/latest/:splat 301 /docs/migration_portal/3.5.1/* /docs/migration_portal/latest/:splat 301 -# FDWs +# FDWs and Connectors /docs/hadoop_data_adapter/2.0/* /docs/hadoop_data_adapter/latest/ 301 /docs/hadoop_data_adapter/2.0.5/* /docs/hadoop_data_adapter/latest/ 301 /docs/jdbc_connector/42.2.12.1/* /docs/jdbc_connector/latest/ 301 /docs/ocl_connector/13.1.4.1/* /docs/ocl_connector/latest/ 301 /docs/odbc_connector/12.0.0.1/* /docs/odbc_connector/latest/ 301 /docs/odbc_connector/12.2.0.1/* /docs/odbc_connector/latest/ 301 +# Collapsed versions +/docs/mysql_data_adapter/2.7.0/* /docs/mongo_data_adapter/2/:splat 301 +/docs/mysql_data_adapter/2.6.0/* /docs/mongo_data_adapter/2/:splat 301 +/docs/mysql_data_adapter/2.5.5/* /docs/mongo_data_adapter/2/:splat 301 # BigAnimal /docs/edbcloud/* /docs/biganimal/:splat 301 From b260d23be83018022aca5ae076a9b06582e4cfcd Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 22 Mar 2022 13:15:45 -0400 Subject: [PATCH 2/2] cleanup and minor nav changes --- .../mysql_data_adapter/2.5.5/01_whats_new.mdx | 13 - .../2.5.5/02_requirements_overview.mdx | 27 - .../2.5.5/03_architecture_overview.mdx | 12 - .../04_installing_the_mysql_data_adapter.mdx | 352 ------------ .../05_updating_the_mysql_data_adapter.mdx | 39 -- .../2.5.5/06_features_of_mysql_fdw.mdx | 67 --- .../07_configuring_the_mysql_data_adapter.mdx | 533 ------------------ ...8_example_using_the_mysql_data_adapter.mdx | 75 --- .../09_example_import_foreign_schema.mdx | 40 -- .../10_identifying_data_adapter_version.mdx | 22 - ...11_uninstalling_the_mysql_data_adapter.mdx | 31 - .../2.5.5/12_troubleshooting.mdx | 21 - .../2.5.5/images/EDB_logo.png | 3 - .../ambari_administrative_interface.png | 3 - .../2.5.5/images/edb_logo.svg | 19 - .../images/mysql_server_with_postgres.png | 3 - .../progress_as_the_servers_restart.png | 3 - .../2.5.5/images/restart_the_server.png | 3 - .../2.5.5/images/setup_wizard_ready.png | 3 - .../specify_an_installation_directory.png | 3 - ...the_installation_wizard_welcome_screen.png | 3 - .../docs/mysql_data_adapter/2.5.5/index.mdx | 22 - .../mysql_data_adapter/2.6.0/01_whats_new.mdx | 10 - .../2.6.0/02_requirements_overview.mdx | 34 -- .../2.6.0/03_architecture_overview.mdx | 9 - .../04_installing_the_mysql_data_adapter.mdx | 480 ---------------- .../05_updating_the_mysql_data_adapter.mdx | 45 -- .../2.6.0/06_features_of_mysql_fdw.mdx | 64 --- .../07_configuring_the_mysql_data_adapter.mdx | 528 ----------------- ...8_example_using_the_mysql_data_adapter.mdx | 72 --- .../09_example_import_foreign_schema.mdx | 37 -- .../2.6.0/10_example_join_push_down.mdx | 102 ---- .../11_identifying_data_adapter_version.mdx | 19 - ...12_uninstalling_the_mysql_data_adapter.mdx | 31 - .../2.6.0/13_troubleshooting.mdx | 18 - .../2.6.0/images/EDB_logo.png | 3 - .../ambari_administrative_interface.png | 3 - .../2.6.0/images/edb_logo.svg | 19 - .../images/mysql_server_with_postgres.png | 3 - .../progress_as_the_servers_restart.png | 3 - .../2.6.0/images/restart_the_server.png | 3 - .../2.6.0/images/setup_wizard_ready.png | 3 - .../specify_an_installation_directory.png | 3 - ...the_installation_wizard_welcome_screen.png | 3 - .../docs/mysql_data_adapter/2.6.0/index.mdx | 15 - .../docs/mysql_data_adapter/2/index.mdx | 14 + 46 files changed, 14 insertions(+), 2804 deletions(-) delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/01_whats_new.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/03_architecture_overview.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/06_features_of_mysql_fdw.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/07_configuring_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/08_example_using_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/09_example_import_foreign_schema.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/10_identifying_data_adapter_version.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/12_troubleshooting.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/images/EDB_logo.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/ambari_administrative_interface.png delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/images/edb_logo.svg delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/mysql_server_with_postgres.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/progress_as_the_servers_restart.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/restart_the_server.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/setup_wizard_ready.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/specify_an_installation_directory.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.5.5/images/the_installation_wizard_welcome_screen.png delete mode 100644 product_docs/docs/mysql_data_adapter/2.5.5/index.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/01_whats_new.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/03_architecture_overview.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/06_features_of_mysql_fdw.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/07_configuring_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/08_example_using_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/09_example_import_foreign_schema.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/10_example_join_push_down.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/11_identifying_data_adapter_version.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/13_troubleshooting.mdx delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/images/EDB_logo.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/ambari_administrative_interface.png delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/images/edb_logo.svg delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/mysql_server_with_postgres.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/progress_as_the_servers_restart.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/restart_the_server.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/setup_wizard_ready.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/specify_an_installation_directory.png delete mode 100755 product_docs/docs/mysql_data_adapter/2.6.0/images/the_installation_wizard_welcome_screen.png delete mode 100644 product_docs/docs/mysql_data_adapter/2.6.0/index.mdx diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/01_whats_new.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/01_whats_new.mdx deleted file mode 100644 index 9cce0e93391..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/01_whats_new.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: "What’s New" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/whats_new.html" ---- - - - -The following features are added to create MySQL Foreign Data Wrapper `2.5.5`: - -- Support for EDB Postgres Advanced Server 13. -- Support for Ubuntu 20.04 LTS platform. diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx deleted file mode 100644 index 15dd425d21d..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/02_requirements_overview.mdx +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: "Requirements Overview" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/requirements_overview.html" ---- - -## Supported Versions - -The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 10 and above. - -## Supported Platforms - -The MySQL Foreign Data Wrapper is supported on the following platforms: - -**Linux x86-64** - - - RHEL 8.x/7.x - - Rocky Linux/AlmaLinux 8.x - - CentOS 7.x - - OL 8.x/7.x - - Ubuntu 20.04/18.04 LTS - - Debian 10.x/9.x - -**Linux on IBM Power8/9 (LE)** - -> - RHEL 7.x diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/03_architecture_overview.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/03_architecture_overview.mdx deleted file mode 100644 index e45a1f384e8..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/03_architecture_overview.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "Architecture Overview" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/architecture_overview.html" ---- - - - -The MySQL data wrapper provides an interface between a MySQL server and a Postgres database. It transforms a Postgres statement (`SELECT`/`INSERT`/`DELETE`/`UPDATE`) into a query that is understood by the MySQL database. - -![Using mysql_fdw with Postgres](images/mysql_server_with_postgres.png) diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx deleted file mode 100644 index 3f04e15e189..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/04_installing_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,352 +0,0 @@ ---- -title: "Installing the MySQL Foreign Data Wrapper" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/installing_the_mysql_data_adapter.html" ---- - - - -The MySQL Foreign Data Wrapper can be installed with an RPM package. During the installation process, the installer will satisfy software prerequisites. - - - -## Installing the MySQL Foreign Data Wrapper using an RPM Package - -You can install the MySQL Foreign Data Wrapper using an RPM package on the following platforms: - -- [RHEL 7](#rhel7) -- [RHEL 8](#rhel8) -- [CentOS 7](#centos7) -- [Rocky Linux/AlmaLinux 8](#centos8) - - - -### On RHEL 7 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` - -Enable the optional, extras, and HA repositories: - - ```text - subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" - ``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -> ```text -> yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -> ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - repo_gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the following command to install the MySQL Foreign Data Wrapper: - - ```text - yum install edb-as-mysql_fdw - ``` - -where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to install MySQL 5.0 on RHEL 7: - - `yum install edb-as-mysql5_fdw` - -!!! Note - MySQL 8.0 and MySQL 5.0 RPMs are available for RHEL 7 platform. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On RHEL 8 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - - ```text - ARCH=$( /bin/arch ) - subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" - ``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - repo_gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: - - ```text - dnf install edb-as-mysql8_fdw - ``` - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On CentOS 7 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - - ```text - yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm - ``` - -!!! Note - You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - -> - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - repo_gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the following command to install the MySQL Foreign Data Wrapper: - - ```text - yum install edb-as-mysql_fdw - ``` - -where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to install MySQL 5.0 on CentOS 7: - - `yum install edb-as-mysql5_fdw` - -!!! Note - MySQL 8.0 and MySQL 5.0 RPMs are available for CentOS 7 platform. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On Rocky Linux/AlmaLinux 8 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - - ```text - dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm - ``` - -Enable the `PowerTools` repository: - - ```text - dnf config-manager --set-enabled PowerTools - ``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - - ```text - dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm - ``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - - ```text - [edb] - name=EnterpriseDB RPMs $releasever - $basearch - baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch - enabled=1 - gpgcheck=1 - repo_gpgcheck=1 - gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY - ``` - -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the following command to install the MySQL Foreign Data Wrapper: - - ```text - dnf install edb-as-mysql8_fdw - ``` - -where `xx` is the server version number. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - -## Installing the MySQL Foreign Data Wrapper on a Debian or Ubuntu Host - -To install the MySQL Foreign Data Wrapper on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit the [EDB website](https://www.enterprisedb.com/repository-access-request/). - -The following steps will walk you through on using the EDB apt repository to install a DEB package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. - -1. Assume superuser privileges: - -```text -sudo su – -``` - -1. Configure the EnterpriseDB repository: - - On Debian 9: - - ```text - sh -c 'echo "deb https://username:password@apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - - On Debian 10: - - 1. Set up the EDB repository: - - ```text - sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - - 1. Substitute your EDB credentials for the `username` and `password` in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -2. Add support to your system for secure APT repositories: - -```text -apt-get install apt-transport-https -``` - -1. Add the EBD signing key: - -```text -wget -q -O - https://username:password -@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - -``` - -1. Update the repository metadata: - -```text -apt-get update -``` - -1. Install DEB package: - -```text -apt-get install edb-as-mysql-fdw -``` - -where `xx` is the server version number. diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx deleted file mode 100644 index 5952e4af7cc..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/05_updating_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: "Updating the MySQL Foreign Data Wrapper" ---- - - - -**Updating an RPM Installation** - -If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: - -- On RHEL or CentOS 7: - - `yum upgrade edb-repo` - -- On RHEL or Rocky Linux or AlmaLinux 8: - - `dnf upgrade edb-repo` - -yum or dnf will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade any installed packages: - -- On RHEL or CentOS 7: - - `yum upgrade edb-as-mysql_fdw` - - where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to upgrade MySQL 5.0 on RHEL 7: - - `yum upgrade edb-as-mysql5_fdw` - -- On RHEL or Rocky Linux or AlmaLinux 8: - - `dnf upgrade edb-as-mysql8_fdw` - -**Updating MongoDB Foreign Data Wrapper on a Debian or Ubuntu Host** - -To update MySQL Foreign Data Wrapper on a Debian or Ubuntu Host, use the following command: - -> `apt-get --only-upgrade install edb-as-mysql_fdw` - -where `xx` is the server version number, and `x` is the supported release version number of MySQL. diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/06_features_of_mysql_fdw.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/06_features_of_mysql_fdw.mdx deleted file mode 100644 index 896169872db..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/06_features_of_mysql_fdw.mdx +++ /dev/null @@ -1,67 +0,0 @@ ---- -title: "Features of the MySQL Foreign Data Wrapper" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/features_of_mysql_fdw.html" ---- - - - -The key features of the MySQL Foreign Data Wrapper are listed below: - -## Writable FDW - -MySQL Foreign Data Wrapper provides the write capability. Users can insert, update and delete data in the remote MySQL tables by inserting, updating and deleting the data locally in the foreign tables. MySQL foreign data wrapper uses the Postgres type casting mechanism to provide opposite type casting between MySQL and Postgres data types. - -!!! Note - The first column of MySQL table must have unique/primary key for DML to work. - -See also: - -[Example: Using the MySQL Foreign Data Wrapper](08_example_using_the_mysql_data_adapter/#example_using_the_mysql_data_adapter) - -[Data Type Mappings](07_configuring_the_mysql_data_adapter/#data-type-mappings) - -## Connection Pooling - -MySQL_FDW establishes a connection to a foreign server during the first query that uses a foreign table associated with the foreign server. This connection is kept and reused for subsequent queries in the same session. - -## Where Clause Push-down - -MySQL Foreign Data Wrapper allows the push-down of `WHERE` clause to the foreign server for execution. This fearure optimizes remote queries to reduce the number of rows transferred from foreign servers. - -## Column Push-down - -MySQL Foreign Data Wrapper supports the column push-down. As a result, the query brings back only those columns that are a part of the select target list. - -## Prepared Statement - -MySQL Foreign Data Wrapper supports Prepared Statement. The select queries uses prepared statements instead of simple query protocol. - -## Import Foreign Schema - -MySQL Foreign Data Wrapper supports Import Foreign Schema which enables the local host to import table definitions on the EDB Postgres Advanced Server from the MySQL server. The new foreign tables are created with the corresponding column types and same table name as that of remote tables in the existing local schema. - -See also: - -[Example: Import Foreign Schema](09_example_import_foreign_schema/#example_import_foreign_schema) - -## Automated Cleanup - -MySQL Foreign Data Wrappper allows the cleanup of foreign tables in a single operation using `DROP EXTENSION` command. This feature is specifically useful when a foreign table is set for a temporary purpose. The syntax: - -> `DROP EXTENSION mysql_fdw CASCADE;` - -For more information, see [DROP EXTENSION](https://www.postgresql.org/docs/current/sql-dropextension.html). - -## Join Push-down - -MySQL Foreign Data Wrapper supports join push-down. It pushes the joins between two foreign tables from the same remote MySQL server to a remote server, thereby enhancing the performance. - -!!! Note - - Currently, joins involving only relational and arithmetic operators in join-clauses are pushed down to avoid any potential join failure. - - Only the INNER and LEFT/RIGHT OUTER joins are supported. - -See also: - -[Example: Join Push-down](10_example_join_push_down/#example_join_push_down) diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/07_configuring_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/07_configuring_the_mysql_data_adapter.mdx deleted file mode 100644 index 55fcc3bf6cd..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/07_configuring_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,533 +0,0 @@ ---- -title: "Configuring the MySQL Foreign Data Wrapper" -redirects: - - '/mysql_data_adapter/2.5.5/06_configuring_the_mysql_data_adapter/' -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/configuring_the_mysql_data_adapter.html" ---- - - - -Before using the MySQL Foreign Data Wrapper, you must: - -> 1. Use the [CREATE EXTENSION](#create-extension) command to create the MySQL Foreign Data Wrapper extension on the Postgres host. -> 2. Use the [CREATE SERVER](#create-server) command to define a connection to the MySQL server. -> 3. Use the [CREATE USER MAPPING](#create-user-mapping) command to define a mapping that associates a Postgres role with the server. -> 4. Use the [CREATE FOREIGN TABLE](#create-foreign-table) command to define a single table in the Postgres database that corresponds to a table that resides on the MySQL server or use the [IMPORT FOREIGN SCHEMA](#import-foreign-schema) command to import multiple remote tables in the local schema. - - - -## CREATE EXTENSION - -Use the `CREATE EXTENSION` command to create the `mysql_fdw` extension. To invoke the command, use your client of choice (for example, psql) to connect to the Postgres database from which you will be querying the MySQL server, and invoke the command: - -```text -CREATE EXTENSION [IF NOT EXISTS] mysql_fdw [WITH] [SCHEMA schema_name]; -``` - -**Parameters** - -`IF NOT EXISTS` - -> Include the `IF NOT EXISTS` clause to instruct the server to issue a notice instead of throwing an error if an extension with the same name already exists. - -`schema_name` - -> Optionally specify the name of the schema in which to install the extension's objects. - -**Example** - -The following command installs the MySQL foreign data wrapper: - -> `CREATE EXTENSION mysql_fdw;` - -For more information about using the foreign data wrapper `CREATE EXTENSION` command, see: - -> . - - - -## CREATE SERVER - -Use the `CREATE SERVER` command to define a connection to a foreign server. The syntax is: - -```text -CREATE SERVER server_name FOREIGN DATA WRAPPER mysql_fdw - [OPTIONS (option 'value' [, ...])] -``` - -The role that defines the server is the owner of the server; use the `ALTER SERVER` command to reassign ownership of a foreign server. To create a foreign server, you must have `USAGE` privilege on the foreign-data wrapper specified in the `CREATE SERVER` command. - -**Parameters** - -`server_name` - -> Use `server_name` to specify a name for the foreign server. The server name must be unique within the database. - -`FOREIGN_DATA_WRAPPER` - -> Include the `FOREIGN_DATA_WRAPPER` clause to specify that the server should use the `mysql_fdw` foreign data wrapper when connecting to the cluster. - -`OPTIONS` - -> Use the `OPTIONS` clause of the `CREATE SERVER` command to specify connection information for the foreign server. You can include: - -| Option | Description | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| host | The address or hostname of the MySQL server. The default value is `127.0.0.1`. | -| port | The port number of the MySQL Server. The default is `3306`. | -| secure_auth | Use to enable or disable secure authentication. The default value is `true`. | -| init_command | The SQL statement to execute when connecting to the MySQL server. | -| ssl_key | The path name of the client private key file. | -| ssl_cert | The path name of the client public key certificate file. | -| ssl_ca | The path name of the Certificate Authority (CA) certificate file. This option, if used, must specify the same certificate used by the server. | -| ssl_capath | The path name of the directory that contains trusted SSL CA certificate files. | -| ssl_cipher | The list of permissible ciphers for SSL encryption. | -| use_remote_estimate | Include the use_remote_estimate to instruct the server to use EXPLAIN commands on the remote server when estimating processing costs. By default, use_remote_estimate is false. | - -**Example** - -The following command creates a foreign server named `mysql_server` that uses the `mysql_fdw` foreign data wrapper to connect to a host with an IP address of `127.0.0.1`: - -```text -CREATE SERVER mysql_server FOREIGN DATA WRAPPER mysql_fdw OPTIONS (host '127.0.0.1', port '3306'); -``` - -The foreign server uses the default port (`3306`) for the connection to the client on the MySQL cluster. - -For more information about using the `CREATE SERVER` command, see: - -> - - - -## CREATE USER MAPPING - -Use the `CREATE USER MAPPING` command to define a mapping that associates a Postgres role with a foreign server: - -```text -CREATE USER MAPPING FOR role_name SERVER server_name - [OPTIONS (option 'value' [, ...])]; -``` - -You must be the owner of the foreign server to create a user mapping for that server. - -**Parameters** - -`role_name` - -> Use `role_name` to specify the role that will be associated with the foreign server. - -`server_name` - -> Use `server_name` to specify the name of the server that defines a connection to the MySQL cluster. - -`OPTIONS` - -> Use the `OPTIONS` clause to specify connection information for the foreign server. -> -> `username`: the name of the user on the MySQL server. -> -> `password`: the password associated with the username. - -**Example** - -The following command creates a user mapping for a role named `enterprisedb`; the mapping is associated with a server named `mysql_server`: - -> `CREATE USER MAPPING FOR enterprisedb SERVER mysql_server;` - -If the database host uses secure authentication, provide connection credentials when creating the user mapping: - -```text -CREATE USER MAPPING FOR public SERVER mysql_server OPTIONS (username 'foo', password 'bar'); -``` - -The command creates a user mapping for a role named `public` that is associated with a server named `mysql_server`. When connecting to the MySQL server, the server will authenticate as `foo`, and provide a password of `bar`. - -For detailed information about the `CREATE USER MAPPING` command, see: - -> - - - -## CREATE FOREIGN TABLE - -A foreign table is a pointer to a table that resides on the MySQL host. Before creating a foreign table definition on the Postgres server, connect to the MySQL server and create a table; the columns in the table will map to columns in a table on the Postgres server. Then, use the `CREATE FOREIGN TABLE` command to define a table on the Postgres server with columns that correspond to the table that resides on the MySQL host. The syntax is: - -```text -CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [ - { column_name data_type [ OPTIONS ( option 'value' [, ... ] ) ] [ COLLATE collation ] [ column_constraint [ ... ] ] - | table_constraint } - [, ... ] -] ) -[ INHERITS ( parent_table [, ... ] ) ] - SERVER server_name [ OPTIONS ( option 'value' [, ... ] ) ] -``` - -where `column_constraint` is: - -```text -[ CONSTRAINT constraint_name ] -{ NOT NULL | NULL | CHECK (expr) [ NO INHERIT ] | DEFAULT default_expr } -``` - -and `table_constraint` is: - -```text -[ CONSTRAINT constraint_name ] CHECK (expr) [ NO INHERIT ] -``` - -**Parameters** - -`table_name` - -> Specifies the name of the foreign table; include a schema name to specify the schema in which the foreign table should reside. - -`IF NOT EXISTS` - -> Include the `IF NOT EXISTS` clause to instruct the server to not throw an error if a table with the same name already exists; if a table with the same name exists, the server will issue a notice. - -`column_name` - -> Specifies the name of a column in the new table; each column should correspond to a column described on the MySQL server. - -`data_type` - -> Specifies the data type of the column; when possible, specify the same data type for each column on the Postgres server and the MySQL server. If a data type with the same name is not available, the Postgres server will attempt to cast the data type to a type compatible with the MySQL server. If the server cannot identify a compatible data type, it will return an error. - -`COLLATE collation` - -> Include the `COLLATE` clause to assign a collation to the column; if not specified, the column data type's default collation is used. - -`INHERITS (parent_table [, ... ])` - -> Include the `INHERITS` clause to specify a list of tables from which the new foreign table automatically inherits all columns. Parent tables can be plain tables or foreign tables. - -`CONSTRAINT constraint_name` - -> Specify an optional name for a column or table constraint; if not specified, the server will generate a constraint name. - -`NOT NULL` - -> Include the `NOT NULL` keywords to indicate that the column is not allowed to contain null values. - -`NULL` - -> Include the `NULL` keywords to indicate that the column is allowed to contain null values. This is the default. - -`CHECK (expr) [NO INHERIT]` - -> Use the `CHECK` clause to specify an expression that produces a Boolean result that each row in the table must satisfy. A check constraint specified as a column constraint should reference that column's value only, while an expression appearing in a table constraint can reference multiple columns. -> -> A `CHECK` expression cannot contain subqueries or refer to variables other than columns of the current row. -> -> Include the `NO INHERIT` keywords to specify that a constraint should not propagate to child tables. - -`DEFAULT default_expr` - -> Include the `DEFAULT` clause to specify a default data value for the column whose column definition it appears within. The data type of the default expression must match the data type of the column. - -`SERVER server_name [OPTIONS (option 'value' [, ... ] ) ]` - -> To create a foreign table that will allow you to query a table that resides on a MySQL file system, include the `SERVER` clause and specify the `server_name` of the foreign server that uses the MySQL data adapter. -> -> Use the `OPTIONS` clause to specify the following `options` and their corresponding values: - -| option | value | -| ------------- | ---------------------------------------------------------------------------------------- | -| dbname | The name of the database on the MySQL server; the database name is required. | -| table_name | The name of the table on the MySQL server; the default is the name of the foreign table. | -| max_blob_size | The maximum blob size to read without truncation. | - -**Example** - -To use data that is stored on MySQL server, you must create a table on the Postgres host that maps the columns of a MySQL table to the columns of a Postgres table. For example, for a MySQL table with the following definition: - -```text -CREATE TABLE warehouse ( - warehouse_id INT PRIMARY KEY, - warehouse_name TEXT, - warehouse_created TIMESTAMP); -``` - -You should execute a command on the Postgres server that creates a comparable table on the Postgres server: - -```text -CREATE FOREIGN TABLE warehouse -( - warehouse_id INT, - warehouse_name TEXT, - warehouse_created TIMESTAMP -) -SERVER mysql_server - OPTIONS (dbname 'db', table_name 'warehouse'); -``` - -Include the `SERVER` clause to specify the name of the database stored on the MySQL server and the name of the table (`warehouse`) that corresponds to the table on the Postgres server. - -For more information about using the `CREATE FOREIGN TABLE` command, see: - -> - -!!! Note - MySQL foreign data wrapper supports the write capability feature. - - - -### Data Type Mappings - -When using the foreign data wrapper, you must create a table on the Postgres server that mirrors the table that resides on the MySQL server. The MySQL data wrapper will automatically convert the following MySQL data types to the target Postgres type: - -| **MySQL** | **Postgres** | -| ----------- | ---------------------------- | -| BIGINT | BIGINT/INT8 | -| BOOLEAN | SMALLINT | -| BLOB | BYTEA | -| CHAR | CHAR | -| DATE | DATE | -| DOUBLE | DOUBLE PRECISION/FLOAT8 | -| FLOAT | FLOAT/FLOAT4 | -| INT/INTEGER | INT/INTEGER/INT4 | -| LONGTEXT | TEXT | -| SMALLINT | SMALLINT/INT2 | -| TIMESTAMP | TIMESTAMP | -| VARCHAR() | VARCHAR()/CHARCTER VARYING() | - -!!! Note - For `ENUM` data type: - - MySQL accepts `enum` value in string form. You must create exactly same `enum` listing on Advanced Server as that is present on MySQL server. Any sort of inconsistency will result in an error while fetching rows with values not known on the local server. - - Also, when the given `enum` value is not present at MySQL side but present at Postgres/Advanced Server side, an empty string (`''`) is inserted as a value at MySQL side for the `enum` column. To select from such a table having enum value as `''`, create an `enum` type at Postgres side with all valid values and `''`. - - - -## IMPORT FOREIGN SCHEMA - -Use the `IMPORT FOREIGN SCHEMA` command to import table definitions on the Postgres server from the MySQL server. The new foreign tables are created with the same column definitions as that of remote tables in the existing local schema. The syntax is: - -```text -IMPORT FOREIGN SCHEMA remote_schema - [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] - FROM SERVER server_name - INTO local_schema - [ OPTIONS ( option 'value' [, ... ] ) ] -``` - -**Parameters** - -`remote_schema` - -Specifies the remote schema (MySQL database) to import from. - -`LIMIT TO ( table_name [, ...] )` - -By default, all views and tables existing in a particular database on the MySQL host are imported. Using this option, you can limit the list of tables to a specified subset. - -`EXCEPT ( table_name [, ...] )` - -By default, all views and tables existing in a particular database on the MySQL host are imported. Using this option, you can exclude specified foreign tables from the import. - -`SERVER server_name` - -Specify the name of server to import foreign tables from. - -`local_schema` - -Specify the name of local schema where the imported foreign tables must be created. - -`OPTIONS` - -Use the `OPTIONS` clause to specify the following `options` and their corresponding values: - -| **Option** | **Description** | -| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -| import_default | Controls whether column `DEFAULT` expressions are included in the definitions of foreign tables imported from a foreign server. The default is `false`. | -| import_not_null | Controls whether column `NOT NULL` constraints are included in the definitions of foreign tables imported from a foreign server. The default is `true`. | - -**Example** - -For a MySQL table created in the `edb` database with the following definition: - -```text -CREATE TABLE color(cid INT PRIMARY KEY, cname TEXT); -INSERT INTO color VALUES (1, 'Red'); -INSERT INTO color VALUES (2, 'Green'); -INSERT INTO color VALUES (3, 'Orange'); - -CREATE TABLE fruit(fid INT PRIMARY KEY, fname TEXT); -INSERT INTO fruit VALUES (1, 'Orange'); -INSERT INTO fruit VALUES (2, 'Mango'); -``` - -You should execute a command on the Postgres server that imports a comparable table on the Postgres server: - -```text -IMPORT FOREIGN SCHEMA edb FROM SERVER mysql_server INTO public; - -SELECT * FROM color; - - cid | cname - -----+-------- - 1 | Red - 2 | Green - 3 | Orange - (3 rows) - -SELECT * FROM fruit; - - fid | fname - -----+-------- - 1 | Orange - 2 | Mango - (2 rows) -``` - -The command imports table definitions from a remote schema `edb` on server `mysql_server` and then creates the foreign tables in local schema `public`. - -For more information about using the `IMPORT FOREIGN SCHEMA` command, see: - -> - -## DROP EXTENSION - -Use the `DROP EXTENSION` command to remove an extension. To invoke the command, use your client of choice (for example, psql) to connect to the Postgres database from which you will be dropping the MySQL server, and run the command: - -```text -DROP EXTENSION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]; -``` - -**Parameters** - -`IF EXISTS` - -> Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if an extension with the specified name doesn't exists. - -`name` - -> Specify the name of the installed extension. It is optional. -> -> `CASCADE` -> -> Automatically drop objects that depend on the extension. It drops all the other dependent objects too. -> -> `RESTRICT` -> -> Do not allow to drop extension if any objects, other than its member objects and extensions listed in the same DROP command are dependent on it. - -**Example** - -The following command removes the extension from the existing database: - -> `DROP EXTENSION mysql_fdw;` - -For more information about using the foreign data wrapper `DROP EXTENSION` command, see: - -> . - -## DROP SERVER - -Use the `DROP SERVER` command to remove a connection to a foreign server. The syntax is: - -```text -DROP SERVER [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] -``` - -The role that drops the server is the owner of the server; use the `ALTER SERVER` command to reassign ownership of a foreign server. To drop a foreign server, you must have `USAGE` privilege on the foreign-data wrapper specified in the `DROP SERVER` command. - -**Parameters** - -`IF EXISTS` - -> Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if a server with the specified name doesn't exists. - -`name` - -> Specify the name of the installed server. It is optional. -> -> `CASCADE` -> -> Automatically drop objects that depend on the server. It should drop all the other dependent objects too. -> -> `RESTRICT` -> -> Do not allow to drop the server if any objects are dependent on it. - -**Example** - -The following command removes a foreign server named `mysql_server`: - -> `DROP SERVER mysql_server;` - -For more information about using the `DROP SERVER` command, see: - -> - -## DROP USER MAPPING - -Use the `DROP USER MAPPING` command to remove a mapping that associates a Postgres role with a foreign server. You must be the owner of the foreign server to remove a user mapping for that server. - -```text -DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC } SERVER server_name; -``` - -**Parameters** - -`IF EXISTS` - -> Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if the user mapping doesn't exist. - -`user_name` - -> Specify the user name of the mapping. - -`server_name` - -> Specify the name of the server that defines a connection to the MySQL cluster. - -**Example** - -The following command drops a user mapping for a role named `enterprisedb`; the mapping is associated with a server named `mysql_server`: - -> `DROP USER MAPPING FOR enterprisedb SERVER mysql_server;` - -For detailed information about the `DROP USER MAPPING` command, see: - -> - -## DROP FOREIGN TABLE - -A foreign table is a pointer to a table that resides on the MySQL host. Use the `DROP FOREIGN TABLE` command to remove a foreign table. Only the owner of the foreign table can drop it. - -```text -DROP FOREIGN TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] -``` - -**Parameters** - -`IF EXISTS` - -> Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if the foreign table with the specified name doesn't exists. - -`name` - -> Specify the name of the foreign table. - -`CASCADE` - -> Automatically drop objects that depend on the foreign table. It should drop all the other dependent objects too. - -`RESTRICT` - -> Do not allow to drop foreign table if any objects are dependent on it. - -**Example** - -```text -DROP FOREIGN TABLE warehouse; -``` - -For more information about using the `DROP FOREIGN TABLE` command, see: - -> diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/08_example_using_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/08_example_using_the_mysql_data_adapter.mdx deleted file mode 100644 index 9f144530b22..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/08_example_using_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,75 +0,0 @@ ---- -title: "Example: Using the MySQL Foreign Data Wrapper" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/example_using_the_mysql_data_adapter.html" ---- - - - -Access data from Advanced Server and connect to psql. Once you are connected to psql, follow the below steps: - -```text --- load extension first time after install -CREATE EXTENSION mysql_fdw; - --- create server object -CREATE SERVER mysql_server - FOREIGN DATA WRAPPER mysql_fdw - OPTIONS (host '127.0.0.1', port '3306'); - --- create user mapping -CREATE USER MAPPING FOR enterprisedb - SERVER mysql_server OPTIONS (username 'foo', password 'bar'); - --- create foreign table -CREATE FOREIGN TABLE warehouse -( - warehouse_id INT, - warehouse_name TEXT, - warehouse_created TIMESTAMP -) -SERVER mysql_server - OPTIONS (dbname 'db', table_name 'warehouse'); - --- insert new rows in table -INSERT INTO warehouse values (1, 'UPS', current_date); -INSERT INTO warehouse values (2, 'TV', current_date); -INSERT INTO warehouse values (3, 'Table', current_date); - --- select from table -SELECT * FROM warehouse ORDER BY 1; - -warehouse_id | warehouse_name | warehouse_created --------------+----------------+------------------- - 1 | UPS | 10-JUL-20 00:00:00 - 2 | TV | 10-JUL-20 00:00:00 - 3 | Table | 10-JUL-20 00:00:00 - --- delete row from table -DELETE FROM warehouse where warehouse_id = 3; - --- update a row of table -UPDATE warehouse set warehouse_name = 'UPS_NEW' where warehouse_id = 1; - --- explain a table with verbose option -EXPLAIN VERBOSE SELECT warehouse_id, warehouse_name FROM warehouse WHERE warehouse_name LIKE 'TV' limit 1; - - QUERY PLAN ----------------------------------------------------------------------------------------------------------------- -Limit (cost=10.00..11.00 rows=1 width=36) - Output: warehouse_id, warehouse_name - -> Foreign Scan on public.warehouse (cost=10.00..1010.00 rows=1000 width=36) - Output: warehouse_id, warehouse_name - Local server startup cost: 10 - Remote query: SELECT `warehouse_id`, `warehouse_name` FROM `db`.`warehouse` WHERE ((`warehouse_name` LIKE BINARY 'TV')) - --- drop foreign table -DROP FOREIGN TABLE warehouse; - --- drop user mapping -DROP USER MAPPING FOR enterprisedb SERVER mysql_server; - --- drop server -DROP SERVER mysql_server; -``` diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/09_example_import_foreign_schema.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/09_example_import_foreign_schema.mdx deleted file mode 100644 index c16df650c06..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/09_example_import_foreign_schema.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: "Example: Import Foreign Schema" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/example_import_foreign_schema.html" ---- - - - -Access data from Advanced Server and connect to psql. Once you are connected to psql, follow the below steps: - -```text --- load extension first time after install -CREATE EXTENSION mysql_fdw; - --- create server object -CREATE SERVER mysql_server - FOREIGN DATA WRAPPER mysql_fdw - OPTIONS (host '127.0.0.1', port '3306'); - --- create user mapping -CREATE USER MAPPING FOR postgres - SERVER mysql_server OPTIONS (username 'foo', password 'bar'); - --- import foreign schema -IMPORT FOREIGN SCHEMA edb FROM SERVER mysql_server INTO public; - - SELECT * FROM color; - cid | cname ------+-------- - 1 | Red - 2 | Green - 3 | Orange - -SELECT * FROM fruit; - fid | fname ------+-------- - 1 | Orange - 2 | Mango -``` diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/10_identifying_data_adapter_version.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/10_identifying_data_adapter_version.mdx deleted file mode 100644 index 2d8d605c401..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/10_identifying_data_adapter_version.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "Identifying the MySQL Foreign Data Wrapper Version" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/identifying_data_adapter_version.html" ---- - - - -The MySQL Foreign Data Wrapper includes a function that you can use to identify the currently installed version of the `.so` file for the data wrapper. To use the function, connect to the Postgres server, and enter: - -```text -SELECT mysql_fdw_version(); -``` - -The function returns the version number: - -```text -mysql_fdw_version ------------------ - -``` diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx deleted file mode 100644 index c9db724cc6a..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/11_uninstalling_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Uninstalling the MySQL Foreign Data Wrapper" ---- - - - -**Uninstalling an RPM Package** - -You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command: - -- On RHEL or CentOS 7: - - `yum remove edb-as-mysql_fdw` - -> where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to uninstall MySQL 5.0 on RHEL 7: -> -> > `yum remove edb-as-mysql5_fdw` - -- On RHEL or Rocky Linux or AlmaLinux 8: - - `dnf remove edb-as-mysql8_fdw` - -Where `xx` is the server version number. - -**Uninstalling MySQL Foreign Data Wrapper on a Debian or Ubuntu Host** - -- To uninstall MySQL Foreign Data Wrapper on a Debian or Ubuntu host, invoke the following command. - - `apt-get remove edb-as-mysql-fdw` - -Where `xx` is the server version number. diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/12_troubleshooting.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/12_troubleshooting.mdx deleted file mode 100644 index be116869731..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/12_troubleshooting.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "Troubleshooting" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/troubleshooting.html" ---- - -In case you are experiencing issues with using MySQL 8 and MySQL_FDW, below is a list of solutions to some frequently seen issues: - -**Authentication plugin ‘caching_sha2_password’ Error** - -```text -ERROR: failed to connect to MySQL: Authentication plugin ‘caching_sha2_password’ cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory -``` - -Specify the authentication plugin as `mysql_native_password` and set a cleartext password value. The syntax: - -> `ALTER USER 'username'@'host' IDENTIFIED WITH mysql_native_password BY '';` - -!!! Note - Refer to [MySQL 8 documentation](https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html) for more details on the above error. diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/EDB_logo.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/EDB_logo.png deleted file mode 100644 index f4a93cf57f5..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/EDB_logo.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07423b012a855204780fe5a2a5a1e33607304a5c3020ae4acbf3d575691dedd6 -size 12136 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/ambari_administrative_interface.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/ambari_administrative_interface.png deleted file mode 100755 index d44e42a740e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/ambari_administrative_interface.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4acb08665b6a1df9494f91f9ab64a8f4d0979f61947e19162f419d134e351ea -size 150222 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/edb_logo.svg b/product_docs/docs/mysql_data_adapter/2.5.5/images/edb_logo.svg deleted file mode 100644 index f24d1dfefee..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/edb_logo.svg +++ /dev/null @@ -1,19 +0,0 @@ - - - edb-logo-disc-dark - - - - \ No newline at end of file diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/mysql_server_with_postgres.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/mysql_server_with_postgres.png deleted file mode 100755 index 0e8e9dfeb4b..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/mysql_server_with_postgres.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84e051f8a6dcf1542939bf2d481c6af6619c94788c107ffe4268aae29eb585be -size 44409 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/progress_as_the_servers_restart.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/progress_as_the_servers_restart.png deleted file mode 100755 index 43523c7d1ad..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/progress_as_the_servers_restart.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:46a0feaf37642c3aa87fe8267259687dfa9c9571f1c2663297159ef98356e2fd -size 85080 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/restart_the_server.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/restart_the_server.png deleted file mode 100755 index 2518b46d46d..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/restart_the_server.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e612201379d56b4dffcfb4222ceb765532ca5d097504c1dbabdc6a812afaba9 -size 33996 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/setup_wizard_ready.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/setup_wizard_ready.png deleted file mode 100755 index 922e318868d..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/setup_wizard_ready.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba6a1a88fe8a91b94571b57a36077fce7b3346e850a38f9bf015166ace93e36 -size 16833 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/specify_an_installation_directory.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/specify_an_installation_directory.png deleted file mode 100755 index 208c85c46af..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/specify_an_installation_directory.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dae28ab7f567617da49816514a3fa5eb6161e611c416295cfe2f829cd941f98e -size 20596 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/images/the_installation_wizard_welcome_screen.png b/product_docs/docs/mysql_data_adapter/2.5.5/images/the_installation_wizard_welcome_screen.png deleted file mode 100755 index 2da19033b0e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/images/the_installation_wizard_welcome_screen.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fd52b490dd37c86dca15975a7dbc9bdd47c7ae4ab0912d1bf570d785c521f79 -size 33097 diff --git a/product_docs/docs/mysql_data_adapter/2.5.5/index.mdx b/product_docs/docs/mysql_data_adapter/2.5.5/index.mdx deleted file mode 100644 index 2647209fbf5..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.5.5/index.mdx +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: "MySQL Foreign Data Wrapper Guide" -legacyRedirectsGenerated: - # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/index.html" - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/conclusion.html" - - "/edb-docs/p/edb-postgres-mysql-data-adapter/2.5.5" - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/whats_new.html" - - "/edb-docs/d/edb-postgres-mysql-data-adapter/user-guides/user-guide/2.5.5/genindex.html" ---- - -The MySQL Foreign Data Wrapper (`mysql_fdw`) is a Postgres extension that allows you to access data that resides on a MySQL database from EDB Postgres Advanced Server. It is a writable foreign data wrapper that you can use with Postgres functions and utilities, or in conjunction with other data that resides on a Postgres host. - -The MySQL Foreign Data Wrapper can be installed with an RPM package. You can download an installer from the [EDB website](https://www.enterprisedb.com/software-downloads-postgres/). - -This guide uses the term `Postgres` to refer to an instance of EDB Postgres Advanced Server. - -
- -whats_new requirements_overview architecture_overview installing_the_mysql_data_adapter updating_the_mysql_data_adapter features_of_mysql_fdw configuring_the_mysql_data_adapter example_using_the_mysql_data_adapter example_import_foreign_schema example_join_push_down identifying_data_adapter_version uninstalling_the_mysql_data_adapter troubleshooting conclusion - -
diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/01_whats_new.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/01_whats_new.mdx deleted file mode 100644 index baeb71f818e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/01_whats_new.mdx +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: "What’s New" ---- - - - -The following feature is added to create MySQL Foreign Data Wrapper `2.6.0`: - -- Support for push down joins to the remote MySQL servers. - diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx deleted file mode 100644 index f3fc9567d24..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/02_requirements_overview.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "Requirements Overview" ---- - -## Supported Versions - -The MySQL Foreign Data Wrapper is certified with EDB Postgres Advanced Server 10 and above. - -## Supported Platforms - -### The MySQL Foreign Data Wrapper is supported for MySQL 8 on the following platforms: - -**Linux x86-64** - -- RHEL 8.x/7.x -- Rocky Linux/AlmaLinux 8.x -- CentOS 7.x -- OL 8.x/7.x -- Ubuntu 20.04/18.04 LTS -- Debian 10.x/9.x - -### The MySQL Foreign Data Wrapper is supported for MySQL 5 on the following platforms: - -**Linux x86-64** - -- RHEL 7.x -- CentOS 7.x -- OL 7.x -- Ubuntu 18.04 LTS -- Debian 10.x/9.x - -**Linux on IBM Power8/9 (LE)** - -- RHEL 7.x diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/03_architecture_overview.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/03_architecture_overview.mdx deleted file mode 100644 index fba2349b118..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/03_architecture_overview.mdx +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Architecture Overview" ---- - - - -The MySQL data wrapper provides an interface between a MySQL server and a Postgres database. It transforms a Postgres statement (`SELECT`/`INSERT`/`DELETE`/`UPDATE`) into a query that is understood by the MySQL database. - -![Using mysql_fdw with Postgres](images/mysql_server_with_postgres.png) diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx deleted file mode 100644 index e04bbbe2d01..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/04_installing_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,480 +0,0 @@ ---- -title: "Installing the MySQL Foreign Data Wrapper" ---- - - - -The MySQL Foreign Data Wrapper can be installed with an RPM package. During the installation process, the installer will satisfy software prerequisites. - - - -## Installing the MySQL Foreign Data Wrapper using an RPM Package - -You can install the MySQL Foreign Data Wrapper using an RPM package on the following platforms: - -- [RHEL 7](#rhel7) -- [RHEL 7 PPCLE](#centos7_PPCLE) -- [RHEL 8](#rhel8) -- [CentOS 7](#centos7) -- [Rocky Linux/AlmaLinux 8](#centos8) - - - -### On RHEL 7 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -Enable the optional, extras, and HA repositories: - -```text -subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms" --enable "rhel-ha-for-rhel-*-server-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing MySQL Foreign Data Wrapper** - -1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: - - ```text - yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm - ``` - -2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: - - For MySQL 8: - ```text - yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw - ``` - - For MySQL 5: - ```text - yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw - ``` -Where `xx` is the server version number i.e. 13. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On RHEL 7 PPCLE - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: -1. Use the following commands to install Advance Toolchain: -```text -rpm --import https://public.dhe.ibm.com/software/server/POWER/Linux/toolchain/at/redhat/RHEL7/gpg-pubkey-6976a827-5164221b - -cat > /etc/yum.repos.d/advance-toolchain.repo < - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing MySQL Foreign Data Wrapper** - -Use the following command to install the MySQL Foreign Data Wrapper: - ```text - yum install edb-as-mysql5_fdw - ``` -where `xx` is the server version number i.e. 13. - - !!! Note - MySQL 8.0 RPMs are not available for CentOS 7 PPCLE platform. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On RHEL 8 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `codeready-builder-for-rhel-8-\*-rpms` repository: - -```text -ARCH=$( /bin/arch ) -subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms" -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -dnf -y https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the below command to install the MySQL Foreign Data Wrapper: - -```text -dnf install edb-as-mysql8_fdw -``` -Where `xx` is the server version number i.e. 13. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - - -### On CentOS 7 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - -```text -yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm -``` - -!!! Note - You may need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file (located in `/etc/yum.repos.d`). - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -yum -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing MySQL Foreign Data Wrapper** - -1. Before installing MySQL FDW, download and install the MySQL repo using the following commands: - ```text - yum -y install https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm - ``` -2. Use the following command to enable the appropriate subrepository and install the MySQL Foreign data Wrapper: - - For MySQL 8: - ```text - yum -y install --enablerepo=mysql80-community --disablerepo=mysql57-community edb-as-mysql8_fdw - ``` - - For MySQL 5: - ```text - yum -y install --enablerepo=mysql57-community --disablerepo=mysql80-community edb-as-mysql5_fdw - ``` -Where `xx` is the server version number i.e. 13. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - - - -### On Rocky Linux/AlmaLinux 8 - -Before installing the MySQL Foreign Data Wrapper, you must install the following prerequisite packages, and request credentials from EDB: - -Install the `epel-release` package: - -```text -dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Enable the `PowerTools` repository: - -```text -dnf config-manager --set-enabled PowerTools -``` - -You must also have credentials that allow access to the EDB repository. For information about requesting credentials, visit: - - - -After receiving your repository credentials you can: - -1. Create the repository configuration file. -2. Modify the file, providing your user name and password. -3. Install the MySQL Foreign Data Wrapper. - -**Creating a Repository Configuration File** - -To create the repository configuration file, assume superuser privileges, and invoke the following command: - -```text -dnf -y install https://yum.enterprisedb.com/edbrepos/edb-repo-latest.noarch.rpm -``` - -The repository configuration file is named `edb.repo`. The file resides in `/etc/yum.repos.d`. - -**Modifying the file, providing your user name and password** - -After creating the `edb.repo` file, use your choice of editor to ensure that the value of the `enabled` parameter is `1`, and replace the `username` and `password` placeholders in the `baseurl` specification with the name and password of a registered EDB user. - -```text -[edb] -name=EnterpriseDB RPMs $releasever - $basearch -baseurl=https://:@yum.enterprisedb.com/edb/redhat/rhel-$releasever-$basearch -enabled=1 -gpgcheck=1 -repo_gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY -``` - -**Installing MySQL Foreign Data Wrapper** - -After saving your changes to the configuration file, use the following command to install the MySQL Foreign Data Wrapper: - -```text -dnf install edb-as-mysql8_fdw -``` -Where `xx` is the server version number i.e. 13. - -When you install an RPM package that is signed by a source that is not recognized by your system, yum may ask for your permission to import the key to your local server. If prompted, and you are satisfied that the packages come from a trustworthy source, enter `y`, and press `Return` to continue. - -During the installation, yum may encounter a dependency that it cannot resolve. If it does, it will provide a list of the required dependencies that you must manually resolve. - -## Installing the MySQL Foreign Data Wrapper on a Debian or Ubuntu Host - -To install the MySQL Foreign Data Wrapper on a Debian or Ubuntu host, you must have credentials that allow access to the EDB repository. To request credentials for the repository, visit the [EDB website](https://www.enterprisedb.com/repository-access-request/). - -The following steps will walk you through on using the EDB apt repository to install a DEB package. When using the commands, replace the `username` and `password` with the credentials provided by EDB. - -1. Assume superuser privileges: - ```text - sudo su – - ``` - -2. Configure the EnterpriseDB repository: - - On Debian 9: - - ```text - sh -c 'echo "deb https://username:password@apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - - On Debian 10, Ubuntu 18, and Ubuntu 20: - - 1. Set up the EDB repository: - - ```text - sh -c 'echo "deb [arch=amd64] https://apt.enterprisedb.com/$(lsb_release -cs)-edb/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/edb-$(lsb_release -cs).list' - ``` - - 2. Substitute your EDB credentials for the `username` and `password` in the following command: - - ```text - sh -c 'echo "machine apt.enterprisedb.com login password " > /etc/apt/auth.conf.d/edb.conf' - ``` - -3. Add support to your system for secure APT repositories: - - ```text - apt-get install apt-transport-https - ``` - -4. Add the EBD signing key: - - ```text - wget -q -O - https://username:password@apt.enterprisedb.com/edb-deb.gpg.key | apt-key add - - ``` -5. If there is `libmysqlclient-dev` already installed on your system, remove it by using the following command: - ```text - sudo apt-get remove libmysqlclient-dev - ``` - -6. Enable the MySQL repo by using the apporpriate command: -- For Debian 9: - - For MySQL 8: - ```text - sudo echo "deb http://repo.mysql.com/apt/debian/stretch mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - - For MySQL 5: - ```text - sudo echo "deb http://repo.mysql.com/apt/debian/stretch mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - -- For Debian 10: - - For MySQL 8: - ```text - sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - - For MySQL 5: - ```text - sudo echo "deb http://repo.mysql.com/apt/debian/buster mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - -- For Ubuntu 18: - - For MySQL 8: - ```text - sudo echo "deb http://repo.mysql.com/apt/ubuntu/bionic mysql-8.0" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - - For MySQL 5: - ```text - sudo echo "deb http://repo.mysql.com/apt/ubuntu/bionic mysql-5.7" | sudo tee /etc/apt/sources.list.d/mysql.list - ``` - Note that you do not need to enable the MySQL repo on Ubuntu 20. - -7. Add the mysql repo key using the following commands: - - ```text - sudo apt-key adv --keyserver pgp.mit.edu --recv-keys 5072E1F5 - ``` -8. Update the repository metadata: - - ```text - apt-get update - ``` - -9. Install DEB package: - - ```text - apt-get install edb-as-mysql-fdw - ``` - Where `xx` is the server version number i.e. 13 and `y` is the MySQL version i.e. 5 or 8. - - - - - - diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx deleted file mode 100644 index c55733f3c5e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/05_updating_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,45 +0,0 @@ ---- -title: "Updating the MySQL Foreign Data Wrapper" ---- - - - -**Updating an RPM Installation** - -If you have an existing RPM installation of MySQL Foreign Data Wrapper, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. yum or dnf will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum or dnf to upgrade any installed packages: - -- For MySQL 8: - - - On RHEL or CentOS 7: - ```text - sudo yum -y upgrade edb-as-mysql8_fdw* mysql-community-devel - ``` - - On RHEL or Rocky Linux or AlmaLinux 8: - ```text - sudo dnf -y upgrade edb-as-mysql8_fdw* mysql-community-devel - ``` -- For MySQL 5 on RHEL or CentOS 7: - ```text - sudo yum -y upgrade edb-as-mysql5_fdw* mysql-community-devel - ``` - -**Updating MySQL Foreign Data Wrapper on a Debian or Ubuntu Host** - -In the previously released version of MySQL FDW, the package name for MySQL FDW was `edb-as*-mysql-fdw`. In the current release, two separate packages have been made available for MySQL 5 and MySQL 8 i.e `edb-as*-mysql5-fdw` and `edb-as*-mysql8-fdw` Respectively. - -If you are upgrading from MySQL FDW 2.5.5 to 2.6.0 for MySQL 5, then installation of `edb-as*mysql5-fdw` package for version 2.6.0 will automatically remove the previously installed package `edb-as*-mysql-fdw`. - -If you are upgrading from MySQL FDW 2.5.5 to 2.6.0 for MySQL 8, then before installing the `edb-as*-mysql8-fdw` package for version 2.6.0, you need to manually remove the following packages: -- `default-mysqlclient-dev` -- `edb-as*-mysql-fdw` - -Use the following command to upgrade the FDW installation: -- For MySQL 8: - ```text - apt-get upgrade edb-as-mysql8-fdw* - ``` -- For MySQL 5: - ```text - apt-get upgrade edb-as-mysql5-fdw* - ``` -where `xx` is the server version number. diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/06_features_of_mysql_fdw.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/06_features_of_mysql_fdw.mdx deleted file mode 100644 index 36ec2634aec..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/06_features_of_mysql_fdw.mdx +++ /dev/null @@ -1,64 +0,0 @@ ---- -title: "Features of the MySQL Foreign Data Wrapper" ---- - - - -The key features of the MySQL Foreign Data Wrapper are listed below: - -## Writable FDW - -MySQL Foreign Data Wrapper provides the write capability. Users can insert, update and delete data in the remote MySQL tables by inserting, updating and deleting the data locally in the foreign tables. MySQL foreign data wrapper uses the Postgres type casting mechanism to provide opposite type casting between MySQL and Postgres data types. - -!!! Note - The first column of MySQL table must have unique/primary key for DML to work. - -See also: - -[Example: Using the MySQL Foreign Data Wrapper](08_example_using_the_mysql_data_adapter/#example_using_the_mysql_data_adapter) - -[Data Type Mappings](07_configuring_the_mysql_data_adapter/#data-type-mappings) - -## Connection Pooling - -MySQL_FDW establishes a connection to a foreign server during the first query that uses a foreign table associated with the foreign server. This connection is kept and reused for subsequent queries in the same session. - -## Where Clause Push-down - -MySQL Foreign Data Wrapper allows the push-down of `WHERE` clause to the foreign server for execution. This fearure optimizes remote queries to reduce the number of rows transferred from foreign servers. - -## Column Push-down - -MySQL Foreign Data Wrapper supports the column push-down. As a result, the query brings back only those columns that are a part of the select target list. - -## Prepared Statement - -MySQL Foreign Data Wrapper supports Prepared Statement. The select queries uses prepared statements instead of simple query protocol. - -## Import Foreign Schema - -MySQL Foreign Data Wrapper supports Import Foreign Schema which enables the local host to import table definitions on the EDB Postgres Advanced Server from the MySQL server. The new foreign tables are created with the corresponding column types and same table name as that of remote tables in the existing local schema. - -See also: - -[Example: Import Foreign Schema](09_example_import_foreign_schema/#example_import_foreign_schema) - -## Automated Cleanup - -MySQL Foreign Data Wrappper allows the cleanup of foreign tables in a single operation using `DROP EXTENSION` command. This feature is specifically useful when a foreign table is set for a temporary purpose. The syntax: - -> `DROP EXTENSION mysql_fdw CASCADE;` - -For more information, see [DROP EXTENSION](https://www.postgresql.org/docs/current/sql-dropextension.html). - -## Join Push-down - -MySQL Foreign Data Wrapper supports join push-down. It pushes the joins between the foreign tables of the same remote MySQL server to that remote MySQL server, thereby enhancing the performance. - -!!! Note - - Currently, joins involving only relational and arithmetic operators in join-clauses are pushed down to avoid any potential join failure. - - Only the INNER and LEFT/RIGHT OUTER joins are supported. - -See also: - -[Example: Join Push-down](10_example_join_push_down/#example_join_push_down) diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/07_configuring_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/07_configuring_the_mysql_data_adapter.mdx deleted file mode 100644 index 5e0c1010285..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/07_configuring_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,528 +0,0 @@ ---- -title: "Configuring the MySQL Foreign Data Wrapper" ---- - - - -Before using the MySQL Foreign Data Wrapper, you must: - - 1. Use the [CREATE EXTENSION](#create-extension) command to create the MySQL Foreign Data Wrapper extension on the Postgres host. - 2. Use the [CREATE SERVER](#create-server) command to define a connection to the MySQL server. - 3. Use the [CREATE USER MAPPING](#create-user-mapping) command to define a mapping that associates a Postgres role with the server. - 4. Use the [CREATE FOREIGN TABLE](#create-foreign-table) command to define a single table in the Postgres database that corresponds to a table that resides on the MySQL server or use the [IMPORT FOREIGN SCHEMA](#import-foreign-schema) command to import multiple remote tables in the local schema. - - - -## CREATE EXTENSION - -Use the `CREATE EXTENSION` command to create the `mysql_fdw` extension. To invoke the command, use your client of choice (for example, psql) to connect to the Postgres database from which you will be querying the MySQL server, and invoke the command: - -```text -CREATE EXTENSION [IF NOT EXISTS] mysql_fdw [WITH] [SCHEMA schema_name]; -``` - -**Parameters** - -`IF NOT EXISTS` - - Include the `IF NOT EXISTS` clause to instruct the server to issue a notice instead of throwing an error if an extension with the same name already exists. - -`schema_name` - - Optionally specify the name of the schema in which to install the extension's objects. - -**Example** - -The following command installs the MySQL foreign data wrapper: - - `CREATE EXTENSION mysql_fdw;` - -For more information about using the foreign data wrapper `CREATE EXTENSION` command, see: - - . - - - -## CREATE SERVER - -Use the `CREATE SERVER` command to define a connection to a foreign server. The syntax is: - -```text -CREATE SERVER server_name FOREIGN DATA WRAPPER mysql_fdw - [OPTIONS (option 'value' [, ...])] -``` - -The role that defines the server is the owner of the server; use the `ALTER SERVER` command to reassign ownership of a foreign server. To create a foreign server, you must have `USAGE` privilege on the foreign-data wrapper specified in the `CREATE SERVER` command. - -**Parameters** - -`server_name` - - Use `server_name` to specify a name for the foreign server. The server name must be unique within the database. - -`FOREIGN_DATA_WRAPPER` - - Include the `FOREIGN_DATA_WRAPPER` clause to specify that the server should use the `mysql_fdw` foreign data wrapper when connecting to the cluster. - -`OPTIONS` - - Use the `OPTIONS` clause of the `CREATE SERVER` command to specify connection information for the foreign server. You can include: - -| Option | Description | -| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| host | The address or hostname of the MySQL server. The default value is `127.0.0.1`. | -| port | The port number of the MySQL Server. The default is `3306`. | -| secure_auth | Use to enable or disable secure authentication. The default value is `true`. | -| init_command | The SQL statement to execute when connecting to the MySQL server. | -| ssl_key | The path name of the client private key file. | -| ssl_cert | The path name of the client public key certificate file. | -| ssl_ca | The path name of the Certificate Authority (CA) certificate file. This option, if used, must specify the same certificate used by the server. | -| ssl_capath | The path name of the directory that contains trusted SSL CA certificate files. | -| ssl_cipher | The list of permissible ciphers for SSL encryption. | -| use_remote_estimate | Include the use_remote_estimate to instruct the server to use EXPLAIN commands on the remote server when estimating processing costs. By default, use_remote_estimate is false. | - -**Example** - -The following command creates a foreign server named `mysql_server` that uses the `mysql_fdw` foreign data wrapper to connect to a host with an IP address of `127.0.0.1`: - -```text -CREATE SERVER mysql_server FOREIGN DATA WRAPPER mysql_fdw OPTIONS (host '127.0.0.1', port '3306'); -``` - -The foreign server uses the default port (`3306`) for the connection to the client on the MySQL cluster. - -For more information about using the `CREATE SERVER` command, see: - - - - - -## CREATE USER MAPPING - -Use the `CREATE USER MAPPING` command to define a mapping that associates a Postgres role with a foreign server: - -```text -CREATE USER MAPPING FOR role_name SERVER server_name - [OPTIONS (option 'value' [, ...])]; -``` - -You must be the owner of the foreign server to create a user mapping for that server. - -**Parameters** - -`role_name` - - Use `role_name` to specify the role that will be associated with the foreign server. - -`server_name` - - Use `server_name` to specify the name of the server that defines a connection to the MySQL cluster. - -`OPTIONS` - - Use the `OPTIONS` clause to specify connection information for the foreign server. - - `username`: the name of the user on the MySQL server. - - `password`: the password associated with the username. - -**Example** - -The following command creates a user mapping for a role named `enterprisedb`; the mapping is associated with a server named `mysql_server`: - - `CREATE USER MAPPING FOR enterprisedb SERVER mysql_server;` - -If the database host uses secure authentication, provide connection credentials when creating the user mapping: - -```text -CREATE USER MAPPING FOR public SERVER mysql_server OPTIONS (username 'foo', password 'bar'); -``` - -The command creates a user mapping for a role named `public` that is associated with a server named `mysql_server`. When connecting to the MySQL server, the server will authenticate as `foo`, and provide a password of `bar`. - -For detailed information about the `CREATE USER MAPPING` command, see: - - - - - -## CREATE FOREIGN TABLE - -A foreign table is a pointer to a table that resides on the MySQL host. Before creating a foreign table definition on the Postgres server, connect to the MySQL server and create a table; the columns in the table will map to columns in a table on the Postgres server. Then, use the `CREATE FOREIGN TABLE` command to define a table on the Postgres server with columns that correspond to the table that resides on the MySQL host. The syntax is: - -```text -CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [ - { column_name data_type [ OPTIONS ( option 'value' [, ... ] ) ] [ COLLATE collation ] [ column_constraint [ ... ] ] - | table_constraint } - [, ... ] -] ) -[ INHERITS ( parent_table [, ... ] ) ] - SERVER server_name [ OPTIONS ( option 'value' [, ... ] ) ] -``` - -where `column_constraint` is: - -```text -[ CONSTRAINT constraint_name ] -{ NOT NULL | NULL | CHECK (expr) [ NO INHERIT ] | DEFAULT default_expr } -``` - -and `table_constraint` is: - -```text -[ CONSTRAINT constraint_name ] CHECK (expr) [ NO INHERIT ] -``` - -**Parameters** - -`table_name` - - Specifies the name of the foreign table; include a schema name to specify the schema in which the foreign table should reside. - -`IF NOT EXISTS` - - Include the `IF NOT EXISTS` clause to instruct the server to not throw an error if a table with the same name already exists; if a table with the same name exists, the server will issue a notice. - -`column_name` - - Specifies the name of a column in the new table; each column should correspond to a column described on the MySQL server. - -`data_type` - - Specifies the data type of the column; when possible, specify the same data type for each column on the Postgres server and the MySQL server. If a data type with the same name is not available, the Postgres server will attempt to cast the data type to a type compatible with the MySQL server. If the server cannot identify a compatible data type, it will return an error. - -`COLLATE collation` - - Include the `COLLATE` clause to assign a collation to the column; if not specified, the column data type's default collation is used. - -`INHERITS (parent_table [, ... ])` - - Include the `INHERITS` clause to specify a list of tables from which the new foreign table automatically inherits all columns. Parent tables can be plain tables or foreign tables. - -`CONSTRAINT constraint_name` - - Specify an optional name for a column or table constraint; if not specified, the server will generate a constraint name. - -`NOT NULL` - - Include the `NOT NULL` keywords to indicate that the column is not allowed to contain null values. - -`NULL` - - Include the `NULL` keywords to indicate that the column is allowed to contain null values. This is the default. - -`CHECK (expr) [NO INHERIT]` - - Use the `CHECK` clause to specify an expression that produces a Boolean result that each row in the table must satisfy. A check constraint specified as a column constraint should reference that column's value only, while an expression appearing in a table constraint can reference multiple columns. - - A `CHECK` expression cannot contain subqueries or refer to variables other than columns of the current row. - - Include the `NO INHERIT` keywords to specify that a constraint should not propagate to child tables. - -`DEFAULT default_expr` - - Include the `DEFAULT` clause to specify a default data value for the column whose column definition it appears within. The data type of the default expression must match the data type of the column. - -`SERVER server_name [OPTIONS (option 'value' [, ... ] ) ]` - - To create a foreign table that will allow you to query a table that resides on a MySQL file system, include the `SERVER` clause and specify the `server_name` of the foreign server that uses the MySQL data adapter. - - Use the `OPTIONS` clause to specify the following `options` and their corresponding values: - -| option | value | -| ------------- | ---------------------------------------------------------------------------------------- | -| dbname | The name of the database on the MySQL server; the database name is required. | -| table_name | The name of the table on the MySQL server; the default is the name of the foreign table. | -| max_blob_size | The maximum blob size to read without truncation. | - -**Example** - -To use data that is stored on MySQL server, you must create a table on the Postgres host that maps the columns of a MySQL table to the columns of a Postgres table. For example, for a MySQL table with the following definition: - -```text -CREATE TABLE warehouse ( - warehouse_id INT PRIMARY KEY, - warehouse_name TEXT, - warehouse_created TIMESTAMP); -``` - -You should execute a command on the Postgres server that creates a comparable table on the Postgres server: - -```text -CREATE FOREIGN TABLE warehouse -( - warehouse_id INT, - warehouse_name TEXT, - warehouse_created TIMESTAMP -) -SERVER mysql_server - OPTIONS (dbname 'db', table_name 'warehouse'); -``` - -Include the `SERVER` clause to specify the name of the database stored on the MySQL server and the name of the table (`warehouse`) that corresponds to the table on the Postgres server. - -For more information about using the `CREATE FOREIGN TABLE` command, see: - -> - -!!! Note - MySQL foreign data wrapper supports the write capability feature. - - - -### Data Type Mappings - -When using the foreign data wrapper, you must create a table on the Postgres server that mirrors the table that resides on the MySQL server. The MySQL data wrapper will automatically convert the following MySQL data types to the target Postgres type: - -| **MySQL** | **Postgres** | -| ----------- | ---------------------------- | -| BIGINT | BIGINT/INT8 | -| BOOLEAN | SMALLINT | -| BLOB | BYTEA | -| CHAR | CHAR | -| DATE | DATE | -| DOUBLE | DOUBLE PRECISION/FLOAT8 | -| FLOAT | FLOAT/FLOAT4 | -| INT/INTEGER | INT/INTEGER/INT4 | -| LONGTEXT | TEXT | -| SMALLINT | SMALLINT/INT2 | -| TIMESTAMP | TIMESTAMP | -| VARCHAR() | VARCHAR()/CHARCTER VARYING() | - -!!! Note - For `ENUM` data type: - - MySQL accepts `enum` value in string form. You must create exactly same `enum` listing on Advanced Server as that is present on MySQL server. Any sort of inconsistency will result in an error while fetching rows with values not known on the local server. - - Also, when the given `enum` value is not present at MySQL side but present at Postgres/Advanced Server side, an empty string (`''`) is inserted as a value at MySQL side for the `enum` column. To select from such a table having enum value as `''`, create an `enum` type at Postgres side with all valid values and `''`. - - - -## IMPORT FOREIGN SCHEMA - -Use the `IMPORT FOREIGN SCHEMA` command to import table definitions on the Postgres server from the MySQL server. The new foreign tables are created with the same column definitions as that of remote tables in the existing local schema. The syntax is: - -```text -IMPORT FOREIGN SCHEMA remote_schema - [ { LIMIT TO | EXCEPT } ( table_name [, ...] ) ] - FROM SERVER server_name - INTO local_schema - [ OPTIONS ( option 'value' [, ... ] ) ] -``` - -**Parameters** - -`remote_schema` - - Specifies the remote schema (MySQL database) to import from. - -`LIMIT TO ( table_name [, ...] )` - - By default, all views and tables existing in a particular database on the MySQL host are imported. Using this option, you can limit the list of tables to a specified subset. - -`EXCEPT ( table_name [, ...] )` - - By default, all views and tables existing in a particular database on the MySQL host are imported. Using this option, you can exclude specified foreign tables from the import. - -`SERVER server_name` - - Specify the name of server to import foreign tables from. - -`local_schema` - - Specify the name of local schema where the imported foreign tables must be created. - -`OPTIONS` - - Use the `OPTIONS` clause to specify the following `options` and their corresponding values: - - | **Option** | **Description** | - | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | - | import_default | Controls whether column `DEFAULT` expressions are included in the definitions of foreign tables imported from a foreign server. The default is `false`. | - | import_not_null | Controls whether column `NOT NULL` constraints are included in the definitions of foreign tables imported from a foreign server. The default is `true`. | - -**Example** - -For a MySQL table created in the `edb` database with the following definition: - -```text -CREATE TABLE color(cid INT PRIMARY KEY, cname TEXT); -INSERT INTO color VALUES (1, 'Red'); -INSERT INTO color VALUES (2, 'Green'); -INSERT INTO color VALUES (3, 'Orange'); - -CREATE TABLE fruit(fid INT PRIMARY KEY, fname TEXT); -INSERT INTO fruit VALUES (1, 'Orange'); -INSERT INTO fruit VALUES (2, 'Mango'); -``` - -You should execute a command on the Postgres server that imports a comparable table on the Postgres server: - -```text -IMPORT FOREIGN SCHEMA edb FROM SERVER mysql_server INTO public; - -SELECT * FROM color; - - cid | cname - -----+-------- - 1 | Red - 2 | Green - 3 | Orange - (3 rows) - -SELECT * FROM fruit; - - fid | fname - -----+-------- - 1 | Orange - 2 | Mango - (2 rows) -``` - -The command imports table definitions from a remote schema `edb` on server `mysql_server` and then creates the foreign tables in local schema `public`. - -For more information about using the `IMPORT FOREIGN SCHEMA` command, see: - - - -## DROP EXTENSION - -Use the `DROP EXTENSION` command to remove an extension. To invoke the command, use your client of choice (for example, psql) to connect to the Postgres database from which you will be dropping the MySQL server, and run the command: - -```text -DROP EXTENSION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]; -``` - -**Parameters** - -`IF EXISTS` - - Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if an extension with the specified name doesn't exists. - -`name` - - Specify the name of the installed extension. It is optional. - - `CASCADE` - - Automatically drop objects that depend on the extension. It drops all the other dependent objects too. - - `RESTRICT` - - Do not allow to drop extension if any objects, other than its member objects and extensions listed in the same DROP command are dependent on it. - -**Example** - -The following command removes the extension from the existing database: - - `DROP EXTENSION mysql_fdw;` - -For more information about using the foreign data wrapper `DROP EXTENSION` command, see: - - . - -## DROP SERVER - -Use the `DROP SERVER` command to remove a connection to a foreign server. The syntax is: - -```text -DROP SERVER [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] -``` - -The role that drops the server is the owner of the server; use the `ALTER SERVER` command to reassign ownership of a foreign server. To drop a foreign server, you must have `USAGE` privilege on the foreign-data wrapper specified in the `DROP SERVER` command. - -**Parameters** - -`IF EXISTS` - - Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if a server with the specified name doesn't exists. - -`name` - - Specify the name of the installed server. It is optional. - - `CASCADE` - - Automatically drop objects that depend on the server. It should drop all the other dependent objects too. - - `RESTRICT` - - Do not allow to drop the server if any objects are dependent on it. - -**Example** - -The following command removes a foreign server named `mysql_server`: - - `DROP SERVER mysql_server;` - -For more information about using the `DROP SERVER` command, see: - - - -## DROP USER MAPPING - -Use the `DROP USER MAPPING` command to remove a mapping that associates a Postgres role with a foreign server. You must be the owner of the foreign server to remove a user mapping for that server. - -```text -DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC } SERVER server_name; -``` - -**Parameters** - -`IF EXISTS` - - Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if the user mapping doesn't exist. - -`user_name` - - Specify the user name of the mapping. - -`server_name` - - Specify the name of the server that defines a connection to the MySQL cluster. - -**Example** - -The following command drops a user mapping for a role named `enterprisedb`; the mapping is associated with a server named `mysql_server`: - - `DROP USER MAPPING FOR enterprisedb SERVER mysql_server;` - -For detailed information about the `DROP USER MAPPING` command, see: - - - -## DROP FOREIGN TABLE - -A foreign table is a pointer to a table that resides on the MySQL host. Use the `DROP FOREIGN TABLE` command to remove a foreign table. Only the owner of the foreign table can drop it. - -```text -DROP FOREIGN TABLE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ] -``` - -**Parameters** - -`IF EXISTS` - - Include the `IF EXISTS` clause to instruct the server to issue a notice instead of throwing an error if the foreign table with the specified name doesn't exists. - -`name` - - Specify the name of the foreign table. - -`CASCADE` - - Automatically drop objects that depend on the foreign table. It should drop all the other dependent objects too. - -`RESTRICT` - - Do not allow to drop foreign table if any objects are dependent on it. - -**Example** - -```text -DROP FOREIGN TABLE warehouse; -``` - -For more information about using the `DROP FOREIGN TABLE` command, see: - - diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/08_example_using_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/08_example_using_the_mysql_data_adapter.mdx deleted file mode 100644 index 6c802b4334a..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/08_example_using_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,72 +0,0 @@ ---- -title: "Example: Using the MySQL Foreign Data Wrapper" ---- - - - -Access data from Advanced Server and connect to psql. Once you are connected to psql, follow the below steps: - -```text --- load extension first time after install -CREATE EXTENSION mysql_fdw; - --- create server object -CREATE SERVER mysql_server - FOREIGN DATA WRAPPER mysql_fdw - OPTIONS (host '127.0.0.1', port '3306'); - --- create user mapping -CREATE USER MAPPING FOR enterprisedb - SERVER mysql_server OPTIONS (username 'foo', password 'bar'); - --- create foreign table -CREATE FOREIGN TABLE warehouse -( - warehouse_id INT, - warehouse_name TEXT, - warehouse_created TIMESTAMP -) -SERVER mysql_server - OPTIONS (dbname 'db', table_name 'warehouse'); - --- insert new rows in table -INSERT INTO warehouse values (1, 'UPS', current_date); -INSERT INTO warehouse values (2, 'TV', current_date); -INSERT INTO warehouse values (3, 'Table', current_date); - --- select from table -SELECT * FROM warehouse ORDER BY 1; - -warehouse_id | warehouse_name | warehouse_created --------------+----------------+------------------- - 1 | UPS | 10-JUL-20 00:00:00 - 2 | TV | 10-JUL-20 00:00:00 - 3 | Table | 10-JUL-20 00:00:00 - --- delete row from table -DELETE FROM warehouse where warehouse_id = 3; - --- update a row of table -UPDATE warehouse set warehouse_name = 'UPS_NEW' where warehouse_id = 1; - --- explain a table with verbose option -EXPLAIN VERBOSE SELECT warehouse_id, warehouse_name FROM warehouse WHERE warehouse_name LIKE 'TV' limit 1; - - QUERY PLAN ----------------------------------------------------------------------------------------------------------------- -Limit (cost=10.00..11.00 rows=1 width=36) - Output: warehouse_id, warehouse_name - -> Foreign Scan on public.warehouse (cost=10.00..1010.00 rows=1000 width=36) - Output: warehouse_id, warehouse_name - Local server startup cost: 10 - Remote query: SELECT `warehouse_id`, `warehouse_name` FROM `db`.`warehouse` WHERE ((`warehouse_name` LIKE BINARY 'TV')) - --- drop foreign table -DROP FOREIGN TABLE warehouse; - --- drop user mapping -DROP USER MAPPING FOR enterprisedb SERVER mysql_server; - --- drop server -DROP SERVER mysql_server; -``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/09_example_import_foreign_schema.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/09_example_import_foreign_schema.mdx deleted file mode 100644 index 04384d09b1a..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/09_example_import_foreign_schema.mdx +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "Example: Import Foreign Schema" ---- - - - -Access data from Advanced Server and connect to psql. Once you are connected to psql, follow the below steps: - -```text --- load extension first time after install -CREATE EXTENSION mysql_fdw; - --- create server object -CREATE SERVER mysql_server - FOREIGN DATA WRAPPER mysql_fdw - OPTIONS (host '127.0.0.1', port '3306'); - --- create user mapping -CREATE USER MAPPING FOR postgres - SERVER mysql_server OPTIONS (username 'foo', password 'bar'); - --- import foreign schema -IMPORT FOREIGN SCHEMA edb FROM SERVER mysql_server INTO public; - - SELECT * FROM color; - cid | cname ------+-------- - 1 | Red - 2 | Green - 3 | Orange - -SELECT * FROM fruit; - fid | fname ------+-------- - 1 | Orange - 2 | Mango -``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/10_example_join_push_down.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/10_example_join_push_down.mdx deleted file mode 100644 index 251c35fb104..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/10_example_join_push_down.mdx +++ /dev/null @@ -1,102 +0,0 @@ ---- -title: "Example: Join Push-down" ---- - - - -The following example shows join push-down between two foreign tables 'warehouse' and 'sales_records': - -Table on MySQL server: - -```text -CREATE TABLE warehouse -( -warehouse_id INT PRIMARY KEY, -warehouse_name TEXT, -warehouse_created TIMESTAMP -); - -CREATE TABLE sales_records -( -warehouse_id INT PRIMARY KEY, -qty INT -); -``` - -Table on Postgres server: - -```text -CREATE EXTENSION mysql_fdw; -CREATE SERVER mysql_server FOREIGN DATA WRAPPER mysql_fdw OPTIONS (host '127.0.0.1', port '3306'); -CREATE USER MAPPING FOR public SERVER mysql_server OPTIONS (username 'edb', password 'edb'); - -CREATE FOREIGN TABLE warehouse -( -warehouse_id INT, -warehouse_name TEXT, -warehouse_created TIMESTAMP -) -SERVER mysql_server OPTIONS (dbname 'edb', table_name 'warehouse'); -INSERT INTO warehouse values (1, 'UPS', current_date); -INSERT INTO warehouse values (2, 'TV', current_date); -INSERT INTO warehouse values (3, 'Table', current_date); - -CREATE FOREIGN TABLE sales_records -( -warehouse_id INT, -qty INT -) -SERVER mysql_server OPTIONS (dbname 'edb', table_name 'sales_records'); -INSERT INTO sales_records values (1, 100); -INSERT INTO sales_records values (2, 75); -INSERT INTO sales_records values (3, 200); -``` - -The output: - -```text ---inner join -edb=# EXPLAIN VERBOSE SELECT t1.warehouse_name, t2.qty FROM warehouse t1 INNER JOIN sales_records t2 ON (t1.warehouse_id = t2.warehouse_id); - QUERY PLAN ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- - Foreign Scan (cost=15.00..35.00 rows=5000 width=36) - Output: t1.warehouse_name, t2.qty - Relations: (edb.warehouse t1) INNER JOIN (edb.sales_records t2) - Local server startup cost: 10 - Remote query: SELECT r1.`warehouse_name`, r2.`qty` FROM (`edb`.`warehouse` r1 INNER JOIN `edb`.`sales_records` r2 ON (((r1.`warehouse_id` = r2.`warehouse_id`)))) -(5 rows) - ---left join -edb=# EXPLAIN VERBOSE SELECT t1.warehouse_name, t2.qty FROM warehouse t1 LEFT JOIN sales_records t2 ON (t1.warehouse_id = t2.warehouse_id); - QUERY PLAN --------------------------------------------------------------------------------------------------------------------------------------------------------------------- - Foreign Scan (cost=15.00..35.00 rows=5000 width=36) - Output: t1.warehouse_name, t2.qty - Relations: (edb.warehouse t1) LEFT JOIN (edb.sales_records t2) - Local server startup cost: 10 - Remote query: SELECT r1.`warehouse_name`, r2.`qty` FROM (`edb`.`warehouse` r1 LEFT JOIN `edb`.`sales_records` r2 ON (((r1.`warehouse_id` = r2.`warehouse_id`)))) -(5 rows) - ---right join -edb=# EXPLAIN VERBOSE SELECT t1.warehouse_name, t2.qty FROM warehouse t1 RIGHT JOIN sales_records t2 ON (t1.warehouse_id = t2.warehouse_id); - QUERY PLAN --------------------------------------------------------------------------------------------------------------------------------------------------------------------- - Foreign Scan (cost=15.00..35.00 rows=5000 width=36) - Output: t1.warehouse_name, t2.qty - Relations: (edb.sales_records t2) LEFT JOIN (edb.warehouse t1) - Local server startup cost: 10 - Remote query: SELECT r1.`warehouse_name`, r2.`qty` FROM (`edb`.`sales_records` r2 LEFT JOIN `edb`.`warehouse` r1 ON (((r1.`warehouse_id` = r2.`warehouse_id`)))) -(5 rows) - ---cross join -edb=# EXPLAIN VERBOSE SELECT t1.warehouse_name, t2.qty FROM warehouse t1 CROSS JOIN -sales_records t2; - QUERY PLAN --------------------------------------------------------------------------------------------------------------------------------- - Foreign Scan (cost=15.00..35.00 rows=1000000 width=36) - Output: t1.warehouse_name, t2.qty - Relations: (edb.warehouse t1) INNER JOIN (edb.sales_records t2) - Local server startup cost: 10 - Remote query: SELECT r1.`warehouse_name`, r2.`qty` FROM (`edb`.`warehouse` r1 INNER JOIN `edb`.`sales_records` r2 ON (TRUE)) -(5 rows) -``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/11_identifying_data_adapter_version.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/11_identifying_data_adapter_version.mdx deleted file mode 100644 index 668f438a89f..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/11_identifying_data_adapter_version.mdx +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: "Identifying the MySQL Foreign Data Wrapper Version" ---- - - - -The MySQL Foreign Data Wrapper includes a function that you can use to identify the currently installed version of the `.so` file for the data wrapper. To use the function, connect to the Postgres server, and enter: - -```text -SELECT mysql_fdw_version(); -``` - -The function returns the version number: - -```text -mysql_fdw_version ------------------ - -``` diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx deleted file mode 100644 index a290dbfea07..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/12_uninstalling_the_mysql_data_adapter.mdx +++ /dev/null @@ -1,31 +0,0 @@ ---- -title: "Uninstalling the MySQL Foreign Data Wrapper" ---- - - - -**Uninstalling an RPM Package** - -You can use the `yum remove` or `dnf remove` command to remove a package installed by `yum` or `dnf`. To remove a package, open a terminal window, assume superuser privileges, and enter the command: - -- On RHEL or CentOS 7: - - `yum remove edb-as-mysql_fdw` - -Where `xx` is the server version number, and `x` is the supported release version number of MySQL. For example, to uninstall MySQL 5.0 on RHEL 7: - - `yum remove edb-as-mysql5_fdw` - -- On RHEL or Rocky Linux or AlmaLinux 8: - - `dnf remove edb-as-mysql8_fdw` - -Where `xx` is the server version number. - -**Uninstalling MySQL Foreign Data Wrapper on a Debian or Ubuntu Host** - -- To uninstall MySQL Foreign Data Wrapper on a Debian or Ubuntu host, invoke the following command: - - `apt-get remove edb-as-mysql-fdw` - -Where `xx` is the server version number. diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/13_troubleshooting.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/13_troubleshooting.mdx deleted file mode 100644 index 2b4ba0109ea..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/13_troubleshooting.mdx +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: "Troubleshooting" ---- - -In case you are experiencing issues with using MySQL 8 and MySQL_FDW, below is a list of solutions to some frequently seen issues: - -**Authentication plugin ‘caching_sha2_password’ Error** - -```text -ERROR: failed to connect to MySQL: Authentication plugin ‘caching_sha2_password’ cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory -``` - -Specify the authentication plugin as `mysql_native_password` and set a cleartext password value. The syntax: - -> `ALTER USER 'username'@'host' IDENTIFIED WITH mysql_native_password BY '';` - -!!! Note - Refer to [MySQL 8 documentation](https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html) for more details on the above error. diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/EDB_logo.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/EDB_logo.png deleted file mode 100644 index f4a93cf57f5..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/EDB_logo.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07423b012a855204780fe5a2a5a1e33607304a5c3020ae4acbf3d575691dedd6 -size 12136 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/ambari_administrative_interface.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/ambari_administrative_interface.png deleted file mode 100755 index d44e42a740e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/ambari_administrative_interface.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4acb08665b6a1df9494f91f9ab64a8f4d0979f61947e19162f419d134e351ea -size 150222 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/edb_logo.svg b/product_docs/docs/mysql_data_adapter/2.6.0/images/edb_logo.svg deleted file mode 100644 index f24d1dfefee..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/edb_logo.svg +++ /dev/null @@ -1,19 +0,0 @@ - - - edb-logo-disc-dark - - - - \ No newline at end of file diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/mysql_server_with_postgres.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/mysql_server_with_postgres.png deleted file mode 100755 index 0e8e9dfeb4b..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/mysql_server_with_postgres.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84e051f8a6dcf1542939bf2d481c6af6619c94788c107ffe4268aae29eb585be -size 44409 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/progress_as_the_servers_restart.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/progress_as_the_servers_restart.png deleted file mode 100755 index 43523c7d1ad..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/progress_as_the_servers_restart.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:46a0feaf37642c3aa87fe8267259687dfa9c9571f1c2663297159ef98356e2fd -size 85080 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/restart_the_server.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/restart_the_server.png deleted file mode 100755 index 2518b46d46d..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/restart_the_server.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e612201379d56b4dffcfb4222ceb765532ca5d097504c1dbabdc6a812afaba9 -size 33996 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/setup_wizard_ready.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/setup_wizard_ready.png deleted file mode 100755 index 922e318868d..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/setup_wizard_ready.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba6a1a88fe8a91b94571b57a36077fce7b3346e850a38f9bf015166ace93e36 -size 16833 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/specify_an_installation_directory.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/specify_an_installation_directory.png deleted file mode 100755 index 208c85c46af..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/specify_an_installation_directory.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dae28ab7f567617da49816514a3fa5eb6161e611c416295cfe2f829cd941f98e -size 20596 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/images/the_installation_wizard_welcome_screen.png b/product_docs/docs/mysql_data_adapter/2.6.0/images/the_installation_wizard_welcome_screen.png deleted file mode 100755 index 2da19033b0e..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/images/the_installation_wizard_welcome_screen.png +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fd52b490dd37c86dca15975a7dbc9bdd47c7ae4ab0912d1bf570d785c521f79 -size 33097 diff --git a/product_docs/docs/mysql_data_adapter/2.6.0/index.mdx b/product_docs/docs/mysql_data_adapter/2.6.0/index.mdx deleted file mode 100644 index d882c59bbe2..00000000000 --- a/product_docs/docs/mysql_data_adapter/2.6.0/index.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: "MySQL Foreign Data Wrapper Guide" ---- - -The MySQL Foreign Data Wrapper (`mysql_fdw`) is a Postgres extension that allows you to access data that resides on a MySQL database from EDB Postgres Advanced Server. It is a writable foreign data wrapper that you can use with Postgres functions and utilities, or in conjunction with other data that resides on a Postgres host. - -The MySQL Foreign Data Wrapper can be installed with an RPM package. You can download an installer from the [EDB website](https://www.enterprisedb.com/software-downloads-postgres/). - -This guide uses the term `Postgres` to refer to an instance of EDB Postgres Advanced Server. - -
- -whats_new requirements_overview architecture_overview installing_the_mysql_data_adapter updating_the_mysql_data_adapter features_of_mysql_fdw configuring_the_mysql_data_adapter example_using_the_mysql_data_adapter example_import_foreign_schema identifying_data_adapter_version troubleshooting conclusion - -
diff --git a/product_docs/docs/mysql_data_adapter/2/index.mdx b/product_docs/docs/mysql_data_adapter/2/index.mdx index 523d4b7095a..946b97e0933 100644 --- a/product_docs/docs/mysql_data_adapter/2/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/index.mdx @@ -2,6 +2,20 @@ title: "MySQL Foreign Data Wrapper" navigation: - mysql_rel_notes +- 02_requirements_overview +- 03_architecture_overview +- 04_installing_the_mysql_data_adapter +- 07_configuring_the_mysql_data_adapter +- 05_updating_the_mysql_data_adapter +- 06_features_of_mysql_fdw +- 08_example_using_the_mysql_data_adapter +- 09_example_import_foreign_schema +- 10_example_join_push_down +- 10a_example_aggregate_func_push_down +- 11_identifying_data_adapter_version +- 13_troubleshooting +- 12_uninstalling_the_mysql_data_adapter + --- The MySQL Foreign Data Wrapper (`mysql_fdw`) is a Postgres extension that allows you to access data that resides on a MySQL database from EDB Postgres Advanced Server. It is a writable foreign data wrapper that you can use with Postgres functions and utilities, or in conjunction with other data that resides on a Postgres host.