| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Improve CREATE POLICY documentation |
| Date: | 2015-12-15 15:08:37 |
| Message-ID: | E1a8rDR-00022p-88@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Improve CREATE POLICY documentation
Clarify that SELECT policies are now applied when SELECT rights
are required for a given query, even if the query is an UPDATE or
DELETE query. Pointed out by Noah.
Additionally, note the risk regarding concurrently open transactions
where a relation which controls access to the rows of another relation
are updated and the rows of the primary relation are also being
modified. Pointed out by Peter Geoghegan.
Back-patch to 9.5.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/43cd468cf01007f39312af05c4c92ceb6de8afd8
Modified Files
--------------
doc/src/sgml/ref/create_policy.sgml | 113 ++++++++++++++++++++++++++---------
1 file changed, 86 insertions(+), 27 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-12-15 16:49:03 | pgsql: Provide a way to predefine LWLock tranche IDs. |
| Previous Message | Stephen Frost | 2015-12-15 01:06:07 | pgsql: Collect the global OR of hasRowSecurity flags for plancache |