|From:||Peter Geoghegan <pg(at)heroku(dot)com>|
|To:||Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Cc:||Stephen Frost <sfrost(at)snowman(dot)net>|
|Subject:||INSERT ... ON CONFLICT UPDATE and RLS|
|Views:||Raw Message | Whole Thread | Download mbox|
The patch that implements INSERT ... ON CONFLICT UPDATE has support
and tests for per-column privileges (which are not relevant to the
IGNORE variant, AFAICT). However, RLS support is another thing
entirely. It has not been properly thought out, and unlike per-column
privileges requires careful consideration, as the correct behavior
I've documented the current problems with RLS here:
It's not clear whether or not the auxiliary UPDATE within an INSERT...
ON CONFLICT UPDATE statement should have security quals appended.
Stephen seemed to think that that might not be the best solution .
I am not sure. I'd like to learn what other people think.
What is the best way of integrating RLS with ON CONFLICT UPDATE? What
behavior is most consistent with the guarantees of RLS? In particular,
should the implementation append security quals to the auxiliary
UPDATE, or fail sooner?
|Next Message||Tom Lane||2015-01-05 17:54:41||Re: Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs|
|Previous Message||Heikki Linnakangas||2015-01-05 17:38:43||Re: pg_rewind in contrib|