]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Protect dblink from invalid options when using postgres_fdw server
authorJoe Conway <mail@joeconway.com>
Thu, 22 Dec 2016 17:19:18 +0000 (09:19 -0800)
committerJoe Conway <mail@joeconway.com>
Thu, 22 Dec 2016 17:19:18 +0000 (09:19 -0800)
commitd5c05f27a43fd0bc777b13dd50de203bade2118d
treef4a9c53b4e623c93391dce9da4acc0d6f6cf4436
parent1cfdb29c7d6621f81d3835e20fd846552c08ec9a
Protect dblink from invalid options when using postgres_fdw server

When dblink uses a postgres_fdw server name for its connection, it
is possible for the connection to have options that are invalid
with dblink (e.g. "updatable"). The recommended way to avoid this
problem is to use dblink_fdw servers instead. However there are use
cases for using postgres_fdw, and possibly other FDWs, for dblink
connection options, therefore protect against trying to use any
options that do not apply by using is_valid_dblink_option() when
building the connection string from the options.

Back-patch to 9.3. Although 9.2 supports FDWs for connection info,
is_valid_dblink_option() did not yet exist, and neither did
postgres_fdw, at least in the postgres source tree. Given the lack
of previous complaints, fixing that seems too invasive/not worth it.

Author: Corey Huinker
Reviewed-By: Joe Conway
Discussion: https://postgr.es/m/CADkLM%3DfWyXVEyYcqbcRnxcHutkP45UHU9WD7XpdZaMfe7S%3DRwA%40mail.gmail.com
contrib/dblink/dblink.c