postgres/contrib/postgres_fdw
Tom Lane d86a2b7b58 Re-establish postgres_fdw connections after server or user mapping changes.
Previously, postgres_fdw would keep on using an existing connection even
if the user did ALTER SERVER or ALTER USER MAPPING commands that should
affect connection parameters.  Teach it to watch for catcache invals
on these catalogs and re-establish connections when the relevant catalog
entries change.  Per bug #14738 from Michal Lis.

In passing, clean up some rather crufty decisions in commit ae9bfc5d6
about where fields of ConnCacheEntry should be reset.  We now reset
all the fields whenever we open a new connection.

Kyotaro Horiguchi, reviewed by Ashutosh Bapat and myself.
Back-patch to 9.3 where postgres_fdw appeared.

Discussion: https://postgr.es/m/20170710113917.7727.10247@wrigleys.postgresql.org
2017-07-21 12:51:38 -04:00
..
expected Re-establish postgres_fdw connections after server or user mapping changes. 2017-07-21 12:51:38 -04:00
sql Re-establish postgres_fdw connections after server or user mapping changes. 2017-07-21 12:51:38 -04:00
.gitignore
connection.c Re-establish postgres_fdw connections after server or user mapping changes. 2017-07-21 12:51:38 -04:00
deparse.c Fix assorted fallout from IS [NOT] NULL patch. 2016-07-28 16:09:15 -04:00
Makefile Allow postgres_fdw to ship extension funcs/operators for remote execution. 2015-11-03 18:42:18 -05:00
option.c pgindent run for 9.6 2016-06-09 18:02:36 -04:00
postgres_fdw--1.0.sql
postgres_fdw.c postgres_fdw: Fix join push down with extensions 2017-04-26 09:14:21 -04:00
postgres_fdw.control
postgres_fdw.h pgindent run for 9.6 2016-06-09 18:02:36 -04:00
shippable.c Update copyright for 2016 2016-01-02 13:33:40 -05:00