| 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 |
| Date: | 2015-07-21 18:14:55 |
| Message-ID: | etPan.55ae8c1f.19495cff.4a53@Butterfly.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On July 21, 2015 at 11:07:36 AM, Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
I'm inclined to think that it's not really necessary to worry about
invalidating a per-connection cache of "is this function safe to ship"
determinations.
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.
Yes?
P.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-21 18:22:02 | Re: [PATCH] postgres_fdw extension support |
| Previous Message | Jim Nasby | 2015-07-21 18:11:27 | Re: First Aggregate Funtion? |