Match pg_user_mappings limits to information_schema.user_mapping_options.
authorNoah Misch <[email protected]>
Mon, 8 May 2017 14:24:24 +0000 (07:24 -0700)
committerNoah Misch <[email protected]>
Mon, 8 May 2017 14:24:28 +0000 (07:24 -0700)
commit99cbb0bd9abc4c3b85a2de2f2e83b5ddc5d38d35
treeefd5a8354b62c01c384974bb91b0ade133c25f46
parent47864be33ccfd8b7334692871fd098596be318e9
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
doc/src/sgml/catalogs.sgml
src/backend/catalog/system_views.sql
src/test/regress/expected/foreign_data.out
src/test/regress/expected/rules.out
src/test/regress/sql/foreign_data.sql