Commit ID cd30728fb2ed7c367d545fc14ab850b5fa2a4850
|Contributor:||Robert Haas||Files Modified:||28|
|Date:||14-February-2012 at 03:20||Lines Added:||2782|
|Repository:||git://git.postgresql.org/git/postgresql.git master||Lines Removed:||2404|
|Commit Comment:||Allow LEAKPROOF functions for better performance of security views.
We don't normally allow quals to be pushed down into a view created
with the security_barrier option, but functions without side effects
are an exception: they're OK. This allows much better performance in
common cases, such as when using an equality operator (that might
even be indexable).
There is an outstanding issue here with the CREATE FUNCTION / ALTER
FUNCTION syntax: there's no way to use ALTER FUNCTION to unset the
leakproof flag. But I'm committing this as-is so that it doesn't
have to be rebased again; we can fix up the grammar in a future
KaiGai Kohei, with some wordsmithing by me.
|File||Language||Code Added||Code Removed||Comments Added||Comment Removed||Blanks Added||Blanks Removed|
|doc/src/sgml/catalogs.sgml||No source code was detected in this file.|
|doc/src/sgml/ref/alter_function.sgml||No source code was detected in this file.|
|doc/src/sgml/ref/create_function.sgml||No source code was detected in this file.|
|doc/src/sgml/rules.sgml||No source code was detected in this file.|