| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 14:38:39 |
| Message-ID: | 20140313143839.GJ8268@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-03-13 10:26:11 -0400, Tom Lane wrote:
> [ forgot to respond to this part ]
>
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> > They currently don't seem to create invalidations on the objects they
> > are set upon, maybe we should change that?
>
> No, because relcache doesn't store security labels to start with.
> There's a separate catalog cache for security labels, I believe,
> and invalidating entries in that ought to be sufficient.
There doesn't seem to be any form of system managed cache for security
labels afaics. Every lookup does a index scan. I currently don't see how
I could build a cache in userland that'd invalidate if either a) the
underlying object changes b) the label changes.
I don't have a better idea than triggering invalidations on the
respective underlying object. If you have one...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-03-13 14:40:19 | Re: [PATCH] Store Extension Options |
| Previous Message | Robert Haas | 2014-03-13 14:37:26 | Re: [PATCH] Store Extension Options |