aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-01-04 12:21:31 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2016-01-04 12:21:41 -0500
commit5d35438273c4523a4dc4b48c3bd575e64310d3d4 (patch)
tree85d72efc1307a3f7276666caba80469ce6eaedfe /src/backend/utils/adt/numeric.c
parent8978eb03a8dcfafd9e0839bc430749839476c34a (diff)
downloadpostgresql-5d35438273c4523a4dc4b48c3bd575e64310d3d4.tar.gz
postgresql-5d35438273c4523a4dc4b48c3bd575e64310d3d4.zip
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.
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions