| From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [PATCH] postgres_fdw extension support |
| Date: | 2015-07-22 19:19:32 |
| Message-ID: | etPan.55afecc8.140e0f76.129ae@Crane.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On July 22, 2015 at 12:15:14 PM, Andres Freund (andres(at)anarazel(dot)de) wrote:
It doesn't seem that unlikely that somebody does an ALTER SERVER OPTIONS
SET .. to add an extension to be shippable while connections are already
using the fdw. It'll be confusing if some clients are fast and some
others are really slow.
This seems more likely than anyone mucking around with extension stuff (adding new functions (and working with FDW in production at the same time?)) or adding/dropping whole extensions (you’ll have more problems than a stale cache, whole columns will disappear if you "DROP EXTENSION postgis CASCADE"), and has the added benefit of not needing me to muck into core stuff for my silly feature.
I’ll have a look at doing invalidation for the case of changes to the FDW wrappers and servers.
P.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-07-22 19:20:33 | Re: BRIN index and aborted transaction |
| Previous Message | Peter Geoghegan | 2015-07-22 19:17:52 | Re: Eliminating CREATE INDEX comparator TID tie-breaker overhead |