Re: unclear about row-level security USING vs. CHECK

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: unclear about row-level security USING vs. CHECK
Дата
Msg-id 5602D551.7080005@gmx.net
обсуждение исходный текст
Ответ на Re: unclear about row-level security USING vs. CHECK  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: unclear about row-level security USING vs. CHECK  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
On 9/23/15 11:05 AM, Stephen Frost wrote:
> That the USING policy is used if WITH CHECK isn't defined?  That was
> simply done to make policy management simple as in quite a few cases
> only one policy is needed.  If a WITH CHECK was always required then
> you'd be constantly writing:
> 
> CREATE POLICY p1 ON t1
> USING (entered_by = current_user)
> WITH CHECK (entered_by = current_user);
> 
> With potentially quite lengthy expressions.

That might be reasonable, but the documentation is completely wrong
about that.

That said, why even have USING and CHECK as separate clauses?  Can't you
just create different policies if you want them different?

Hypothetical example:

CREATE POLICY p1 ON t1 FOR SELECT CHECK (extract(year from entered_on) =
extract(year from current_timestamp));
CREATE POLICY p2 ON t2 FOR INSERT, UPDATE, DELETE CHECK (entered_by =
current_user);



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Parallel Seq Scan
Следующее
От: Tom Lane
Дата:
Сообщение: Re: TEXT vs VARCHAR join qual push down diffrence, bug or expected?