On 21 December 2012 22:01, Stephen Frost <sfr...@snowman.net> wrote: >> On the other hand, we are standing next to the consensus about >> reader-side; a unique row-security policy (so, first version does not >> support per-command policy) shall be checked on table scanning >> on select, update or delete commands. > > I don't feel that we've really reached a consensus about the > 'reader-side' implemented in this patch- rather, we've agreed (at a > pretty high level) what the default impact of RLS for SELECT queries is. > While I'm glad that we were able to do that, I'm rather dismayed that it > took a great deal of discussion to get to that point.
Would anybody like to discuss this on a conference call on say 28th Dec, to see if we can agree a way forwards? I feel certain that we can work through any difficulties and agree a minimal subset for change. All comers welcome, just contact me offlist for details. I've got literally nothing riding on this, other than my desire for progress, so I don't see the need for going too many extra miles if nobody else does. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
