Re: Using views for row-level access control is leaky
От | Richard Huxton |
---|---|
Тема | Re: Using views for row-level access control is leaky |
Дата | |
Msg-id | 4AE03FB7.5050102@archonet.com обсуждение исходный текст |
Ответ на | Re: Using views for row-level access control is leaky (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: Using views for row-level access control is leaky
|
Список | pgsql-hackers |
Pavel Stehule wrote: > 2009/10/22 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>: >> That example I ran on CVS HEAD, but it's a generic problem on all versions. > postgres=# select version(); > version > ──────────────────────────────────────────────────────────────────────────────────── > PostgreSQL 8.5devel on i686-pc-linux-gnu, compiled by GCC gcc (GCC) > 4.4.1 20090725 > (1 row) > > postgres=# select * from x; > a │ b > ────┼──── > 10 │ 20 > (1 row) > > postgres=# create view v as select * from x where b <> 20; ^^^^^^^ This is the expression that needs to be expensive. Then the exposing function needs to be cheap. That makes the planner run the exposing function first. -- Richard Huxton Archonet Ltd
В списке pgsql-hackers по дате отправления: