Match pg_user_mappings limits to information_schema.user_mapping_options.

Noah Misch <noah@leadboat.com>

Commit: c928addfccd7f9905472dddd94e9cd10bc3f6808
Author: Noah Misch <noah@leadboat.com>
Date: 2017-05-08T14:24:27Z
Releases: 9.6.3
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

Files

Documentation touched