aboutsummaryrefslogtreecommitdiff
path: root/src/backend/replication/logical/tablesync.c
diff options
context:
space:
mode:
authorNoah Misch <noah@leadboat.com>2017-05-08 07:24:24 -0700
committerNoah Misch <noah@leadboat.com>2017-05-08 07:24:24 -0700
commit3eefc51053f250837c3115c12f8119d16881a2d7 (patch)
treec626dd3c72e3c47364a9b2e615030ddb1b89b4b8 /src/backend/replication/logical/tablesync.c
parent0170b10dff04e0f50f5522c377a4d10d4424155c (diff)
downloadpostgresql-3eefc51053f250837c3115c12f8119d16881a2d7.tar.gz
postgresql-3eefc51053f250837c3115c12f8119d16881a2d7.zip
Match pg_user_mappings limits to information_schema.user_mapping_options.
Both views replace the umoptions field with NULL when the user does not meet qualifications to see it. They used different qualifications, and pg_user_mappings documented qualifications did not match its implemented qualifications. Make its documentation and implementation match those of user_mapping_options. One might argue for stronger qualifications, but these have long, documented tenure. pg_user_mappings has always exhibited this problem, so back-patch to 9.2 (all supported versions). Michael Paquier and Feike Steenbergen. Reviewed by Jeff Janes. Reported by Andrew Wheelwright. Security: CVE-2017-7486
Diffstat (limited to 'src/backend/replication/logical/tablesync.c')
0 files changed, 0 insertions, 0 deletions