| From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [PATCH] postgres_fdw extension support |
| Date: | 2015-10-06 13:28:34 |
| Message-ID: | CACowWR3cRoqym+N=fxpOrRsYwQemV0SEPKX0VypDeOfHHWFaWA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 6, 2015 at 5:32 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> The problem is basically that cache invalidations can arrive while
> you're building new cache entries. Everytime you e.g. open a relation
> cache invalidations can arrive. Assume you'd written the code like:
> You're avoiding that by only entering into the hashtable *after* the
> lookup. And I think that deserves a comment.
Thanks, revised patch attached.
P.
| Attachment | Content-Type | Size |
|---|---|---|
| 20151006_postgres_fdw_extensions.patch | application/octet-stream | 24.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-10-06 13:32:35 | Re: [PATCH] postgres_fdw extension support |
| Previous Message | David Christensen | 2015-10-06 13:17:02 | [PATCH] Comment fixes |