On Mon, Nov 4, 2013 at 9:37 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Craig Ringer <cr...@2ndquadrant.com> writes: >> On 09/04/2013 11:22 PM, Tom Lane wrote: >>> AFAICT, to deal with update/delete the RLS patch needs to constrain order >>> of qual application without the crutch of having a separate level of >>> subquery; and it's that behavior that I have zero confidence in, either >>> as to whether it works as submitted or as to our odds of not breaking it >>> in the future. > >> Wouldn't CASE do that job, albeit in a somewhat ugly manner, and also >> protect against malicious RLS functions? > > You mean wrap all the query quals in a CASE? Sure, if you didn't mind > totally destroying any optimization possibilities. If you did that, > every table scan would become a seqscan and every join a nestloop.
I'd still like to here what's wrong with what I said here: http://www.postgresql.org/message-id/ca+tgmoyr1phw3x9vnvuwdcfxkzk2p_jhtwc0fv2q58negcx...@mail.gmail.com -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
