|From:||Paul Ramsey <pramsey(at)cleverelephant(dot)ca>|
|To:||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>, Andres Freund <andres(at)anarazel(dot)de>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: [PATCH] postgres_fdw extension support|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On July 21, 2015 at 11:22:12 AM, Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> So: yes to a local cache of all forwardable functions/ops, populated in full the first time through (does that speak maybe to using a binary search on a sorted list instead of a hash, since I only pay the sort price once and am not doing any insertions?). And then we just hold it until the connection goes away.
No, *not* populated first-time-through, because that won't handle any of
the CREATE, DROP, or UPGRADE cases. It's also doing a lot of work you
might never need. I was thinking of "populate on demand", that is, first
time you need to know whether function X is shippable, you find that out
and then cache the answer (whether it be positive or negative).
Roger that. Off to the races..
|Next Message||Fabien COELHO||2015-07-21 18:41:35||Re: pgbench stats per script & other stuff|
|Previous Message||Andres Freund||2015-07-21 18:27:04||Re: [PATCH] postgres_fdw extension support|