aboutsummaryrefslogtreecommitdiff
path: root/src/test/modules/libpq_pipeline/libpq_pipeline.c
diff options
context:
space:
mode:
authorJoe Conway <mail@joeconway.com>2021-03-31 13:55:25 -0400
committerJoe Conway <mail@joeconway.com>2021-03-31 13:55:25 -0400
commitb12bd4869b5e64b742a69ca07915e2f77f85a9ae (patch)
tree44c2f80d86ccabaf46d7489b515a258eaece4f1c /src/test/modules/libpq_pipeline/libpq_pipeline.c
parent86dc90056dfdbd9d1b891718d2e5614e3e432f35 (diff)
downloadpostgresql-b12bd4869b5e64b742a69ca07915e2f77f85a9ae.tar.gz
postgresql-b12bd4869b5e64b742a69ca07915e2f77f85a9ae.zip
Fix has_column_privilege function corner case
According to the comments, when an invalid or dropped column oid is passed to has_column_privilege(), the intention has always been to return NULL. However, when the caller had table level privilege the invalid/missing column was never discovered, because table permissions were checked first. Fix that by introducing extended versions of pg_attribute_acl(check|mask) and pg_class_acl(check|mask) which take a new argument, is_missing. When is_missing is NULL, the old behavior is preserved. But when is_missing is passed by the caller, no ERROR is thrown for dropped or missing columns/relations, and is_missing is flipped to true. This in turn allows has_column_privilege to check for column privileges first, providing the desired semantics. Not backpatched since it is a user visible behavioral change with no previous complaints, and the fix is a bit on the invasive side. Author: Joe Conway Reviewed-By: Tom Lane Reported by: Ian Barwick Discussion: https://postgr.es/m/flat/9b5f4311-157b-4164-7fe7-077b4fe8ed84%40joeconway.com
Diffstat (limited to 'src/test/modules/libpq_pipeline/libpq_pipeline.c')
0 files changed, 0 insertions, 0 deletions