| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Store Extension Options |
| Date: | 2014-03-13 16:11:23 |
| Message-ID: | 1433.1394727083@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-03-13 11:26:10 -0400, Robert Haas wrote:
>> I have however had the thought before that it would be nice to allow
>> for callbacks of invalidation functions of some kind even on catalogs
>> that don't have catcaches.
> Unfortunately the format catcache invalidations have is pretty tightly
> tied to the hash function catcaches use internally. And we need
> something that can be included in the WAL, otherwise it won't work on HS
> nodes.
Note that the existence of a cache doesn't mean it's necessarily
populated. In this example, a catcache on pg_seclabels could be used just
fine, as long as it wasn't used to load labels for large objects. Even if
it were never used at all, it would still provide a usable conduit for
invalidation events.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2014-03-13 16:16:45 | Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns |
| Previous Message | Andrew Dunstan | 2014-03-13 16:04:28 | Re: Postgresql XML parsing |