From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |
Date: | 2010-07-09 17:12:12 |
Message-ID: | 1278695532.29736.719.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Fri, 2010-07-09 at 11:09 -0400, Stephen Frost wrote:
> > Strangely, I was looking into removing the ExecCheckRTPerms check
> > altogether by forcing plan invalidation when permissions are
> updated.
> > That would be a performance tweak that would render this change
> useless.
>
> I don't see how you could remove ExecCheckRTPerms..? It's what
> handles
> all permissions checking for DML (like, making sure you have SELECT
> rights on the table you're trying to query). I could see forcing plan
> invalidation when permissions are updated, sure, but that doesn't mean
> you can stop doing them altogether anywhere. Where would you move the
> permissions checking to?
I apologise, when I said removing the check altogether, I meant removing
from the executor path.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2010-07-09 17:19:31 | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |
Previous Message | Simon Riggs | 2010-07-09 17:07:52 | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2010-07-09 17:18:01 | Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock |
Previous Message | Simon Riggs | 2010-07-09 17:07:52 | Re: [COMMITTERS] pgsql: Add a hook in ExecCheckRTPerms(). |