diff options
| author | Joe Conway <mail@joeconway.com> | 2016-12-22 09:19:44 -0800 |
|---|---|---|
| committer | Joe Conway <mail@joeconway.com> | 2016-12-22 09:20:35 -0800 |
| commit | c4448683893bd37b59003603bc9075d362e81b5a (patch) | |
| tree | e408a8f2fc61a9da47893fd6c8a2650e9bd2157e /src/backend/parser/parse_utilcmd.c | |
| parent | 01ec25631fe0eae6af67c29c61a358dc6b92ed3c (diff) | |
| download | postgresql-c4448683893bd37b59003603bc9075d362e81b5a.tar.gz postgresql-c4448683893bd37b59003603bc9075d362e81b5a.zip | |
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
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions