-
- Downloads
Adjust behavior of row_security GUC to match the docs.
Some time back we agreed that row_security=off should not be a way to bypass RLS entirely, but only a way to get an error if it was being applied. However, the code failed to act that way for table owners. Per discussion, this is a must-fix bug for 9.5.0. Adjust the logic in rls.c to behave as expected; also, modify the error message to be more consistent with the new interpretation. The regression tests need minor corrections as well. Also update the comments about row_security in ddl.sgml to be correct. (The official description of the GUC in config.sgml is already correct.) I failed to resist the temptation to do some other very minor cleanup as well, such as getting rid of a duplicate extern declaration.
Showing
- doc/src/sgml/ddl.sgml 21 additions, 13 deletionsdoc/src/sgml/ddl.sgml
- src/backend/utils/misc/rls.c 27 additions, 23 deletionssrc/backend/utils/misc/rls.c
- src/test/regress/expected/rowsecurity.out 21 additions, 40 deletionssrc/test/regress/expected/rowsecurity.out
- src/test/regress/sql/rowsecurity.sql 9 additions, 16 deletionssrc/test/regress/sql/rowsecurity.sql
Loading
Please register or sign in to comment