MySQL Foreign Data Wrapper for PostgreSQL
This PostgreSQL extension implements a Foreign Data Wrapper (FDW) for MySQL.
Please note that this version of mysql_fdw works with PostgreSQL and EDB Postgres Advanced Server 9.5, 9.6, 10, 11, 12, and 13.
To build on POSIX-compliant systems you need to ensure the
pg_configexecutable is in your path when you run
make. This executable is typically in your PostgreSQL installation's
bindirectory. For example:
$ export PATH=/usr/local/pgsql/bin/:$PATH
mysql_configmust also be in the path, it resides in the MySQL
$ export PATH=/usr/local/mysql/bin/:$PATH
Compile the code using make.
$ make USE_PGXS=1
Finally install the foreign data wrapper.
$ make USE_PGXS=1 install
Running regression test.
$ make USE_PGXS=1 installcheck
However, make sure to set the
MYSQL_PWDenvironment variables correctly. The default settings can be found in the
If you run into any issues, please let us know.
The following enhancements are added to the latest version of
The previous version was only read-only, the latest version provides the write capability. The user can now issue an insert, update, and delete statements for the foreign tables using the mysql_fdw. It uses the PG type casting mechanism to provide opposite type casting between MySQL and PG data types.
The latest version comes with a connection pooler that utilises the same MySQL database connection for all the queries in the same session. The previous version would open a new MySQL database connection for every query. This is a performance enhancement.
WHERE clause push-down
The latest version will push-down the foreign table where clause to the foreign server. The where condition on the foreign table will be executed on the foreign server hence there will be fewer rows to bring across to PostgreSQL. This is a performance feature.
The previous version was fetching all the columns from the target foreign table. The latest version does the column push-down and only brings back the columns that are part of the select target list. This is a performance feature.
select queries to use prepared statement)
select queries are now using prepared statements instead of simple
mysql_fdw now also supports join push-down. The joins between two foreign tables from the same remote MySQL server are pushed to a remote server, instead of fetching all the rows for both the tables and performing a join locally, thereby enhancing the performance. Currently, joins involving only relational and arithmetic operators in join-clauses are pushed down to avoid any potential join failure. Also, only the INNER and LEFT/RIGHT OUTER joins are supported, and not the FULL OUTER, SEMI, and ANTI join. This is a performance feature.
The following parameters can be set on a MySQL foreign server object:
host: Address or hostname of the MySQL server. Defaults to
port: Port number of the MySQL server. Defaults to
secure_auth: Enable or disable secure authentication. Default is
init_command: SQL statement to execute when connecting to the MySQL server.
use_remote_estimate: Controls whether mysql_fdw issues remote EXPLAIN commands to obtain cost estimates. Default is
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.
The following parameters can be set on a MySQL foreign table object:
dbname: Name of the MySQL database to query. This is a mandatory option.
table_name: Name of the MySQL table, default is the same as foreign table.
max_blob_size: Max blob size to read without truncation.
The following parameters need to supplied while creating user mapping.
username: Username to use when connecting to MySQL.
password: Password to authenticate to the MySQL server with.
-- 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'); -- 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'))
If you experience any bug and have a fix for that, or have a new idea, create a ticket on github page. Before creating a pull request please read the contributing guidelines.
This project will be modified to maintain compatibility with new PostgreSQL and EDB Postgres Advanced Server releases.
If you require commercial support, please contact the EnterpriseDB sales team, or check whether your existing PostgreSQL support provider can also support mysql_fdw.
Copyright (c) 2011-2021, EnterpriseDB Corporation.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose, without fee, and without a written agreement is hereby granted, provided that the above copyright notice and this paragraph and the following two paragraphs appear in all copies.
LICENSE file for full details.