Greg Stark <gsst...@mit.edu> writes: > Heikki's point is still valid though. Consider if it's not a matter of > filter ordering but rather that a filter is being pushed down inside a > join. If the join is from the view then it would be unsafe to filter > the rows before seeing which rows match the join... unless we can > prove all the rows survive... It would really suck not to do this > optimization too if for example you have a filter which filters all > but a single row and then join against a large table...
Well, more generally, any restriction whatsoever that is placed on the current planner behavior in the name of security will result in catastrophic performance degradation for some queries. I agree with Robert's nearby comments that we need to be selective about which views we do this to and which functions we distrust. CREATE SECURITY VIEW, anyone? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers