aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/typecmds.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2012-02-13 22:20:27 -0500
committerRobert Haas <rhaas@postgresql.org>2012-02-13 22:21:14 -0500
commitcd30728fb2ed7c367d545fc14ab850b5fa2a4850 (patch)
treec5d487f3abf9e5c66734db8ecb100f4442763822 /src/backend/commands/typecmds.c
parent2bbd88f8f841b01efb073972b60d4dc1ff1f6fd0 (diff)
downloadpostgresql-cd30728fb2ed7c367d545fc14ab850b5fa2a4850.tar.gz
postgresql-cd30728fb2ed7c367d545fc14ab850b5fa2a4850.zip
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 commit. KaiGai Kohei, with some wordsmithing by me.
Diffstat (limited to 'src/backend/commands/typecmds.c')
-rw-r--r--src/backend/commands/typecmds.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/commands/typecmds.c b/src/backend/commands/typecmds.c
index c6bc6c8e876..3523554cfbd 100644
--- a/src/backend/commands/typecmds.c
+++ b/src/backend/commands/typecmds.c
@@ -1521,6 +1521,7 @@ makeRangeConstructors(const char *name, Oid namespace,
false, /* isAgg */
false, /* isWindowFunc */
false, /* security_definer */
+ false, /* leakproof */
false, /* isStrict */
PROVOLATILE_IMMUTABLE, /* volatility */
constructorArgTypesVector, /* parameterTypes */