| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] postgres_fdw extension support |
| Date: | 2015-07-22 18:55:15 |
| Message-ID: | 8773.1437591315@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jul 21, 2015 at 2:27 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> But I'm not going to complain too loudly if we don't do invalidation.
> Not doing invalidation seems silly to me. But I don't want to bend
> Paul too far around the axle, either.
Just to be clear here: the case we are concerned about is, given that
we have determined that function X is or is not a member of one of the
extensions marked "shippable" for a given connection, is it likely that
that status will change (while the function continues to exist with
the same OID) during the lifespan of the connection? If it did change,
how critical would it be for us to honor the new shippability criterion
on that connection? My answer to both is "not very". So I'm not excited
about expending lots of code or cycles to check for such changes.
If we were trying to cache things across more than a connection lifespan,
the answer might be different.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-07-22 19:15:12 | Re: [PATCH] postgres_fdw extension support |
| Previous Message | Alvaro Herrera | 2015-07-22 18:48:31 | Re: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact() |