Again match pg_user_mappings to information_schema.user_mapping_options.
authorNoah Misch
Mon, 7 Aug 2017 14:09:28 +0000 (07:09 -0700)
committerNoah Misch
Mon, 7 Aug 2017 14:09:31 +0000 (07:09 -0700)
commitb6e39ca92eeee4e5fa0e83ce3e04dad82559983f
tree422c9ea9db2e603dd43d11fabfa127cb2084a21c
parentd5d46d99ba47f77a847d29a35d6e069b233f2183
Again match pg_user_mappings to information_schema.user_mapping_options.

Commit 3eefc51053f250837c3115c12f8119d16881a2d7 claimed to make
pg_user_mappings enforce the qualifications user_mapping_options had
been enforcing, but its removal of a longstanding restriction left them
distinct when the current user is the subject of a mapping yet has no
server privileges.  user_mapping_options emits no rows for such a
mapping, but pg_user_mappings includes full umoptions.  Change
pg_user_mappings to show null for umoptions.  Back-patch to 9.2, like
the above commit.

Reviewed by Tom Lane.  Reported by Jeff Janes.

Security: CVE-2017-7547
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