diff options
| author | Noah Misch <noah@leadboat.com> | 2015-10-03 20:19:57 -0400 |
|---|---|---|
| committer | Noah Misch <noah@leadboat.com> | 2015-10-03 20:20:50 -0400 |
| commit | 01ba7894f3f72ea57d1cfdc4f40f6231bc6cd9cd (patch) | |
| tree | 8153ebad55cc49f2cb534ec4be5c2e8f96d3071c /doc/src/sgml/ref | |
| parent | cfddb5df5a84923160b23890d6086bcbcd1fd655 (diff) | |
| download | postgresql-01ba7894f3f72ea57d1cfdc4f40f6231bc6cd9cd.tar.gz postgresql-01ba7894f3f72ea57d1cfdc4f40f6231bc6cd9cd.zip | |
Make BYPASSRLS behave like superuser RLS bypass.
Specifically, make its effect independent from the row_security GUC, and
make it affect permission checks pertinent to views the BYPASSRLS role
owns. The row_security GUC thereby ceases to change successful-query
behavior; it can only make a query fail with an error. Back-patch to
9.5, where BYPASSRLS was introduced.
Diffstat (limited to 'doc/src/sgml/ref')
| -rw-r--r-- | doc/src/sgml/ref/create_role.sgml | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/create_role.sgml b/doc/src/sgml/ref/create_role.sgml index f4a176bff3f..240c21ce85f 100644 --- a/doc/src/sgml/ref/create_role.sgml +++ b/doc/src/sgml/ref/create_role.sgml @@ -196,16 +196,13 @@ CREATE ROLE <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replac <term><literal>NOBYPASSRLS</literal></term> <listitem> <para> - These clauses determine whether a role is allowed to bypass row-level security (RLS) - policies. A role having the <literal>BYPASSRLS</literal> attribute will - be allowed to bypass row-security policies by setting - <literal>row_security</literal> to - <literal>OFF</literal>. <literal>NOBYPASSRLS</literal> is the default. + These clauses determine whether a role bypasses every row-level + security (RLS) policy. <literal>NOBYPASSRLS</literal> is the default. Note that pg_dump will set <literal>row_security</literal> to <literal>OFF</literal> by default, to ensure all contents of a table are dumped out. If the user running pg_dump does not have appropriate permissions, an error will be returned. The superuser and owner of the - table being dumped are considered to always have the right to bypass RLS. + table being dumped always bypass RLS. </para> </listitem> </varlistentry> |