You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Revise the permission checking on user mapping DDL commands.
CREATE/ALTER/DROP USER MAPPING are now allowed either by the server owner orby a user with USAGE privileges for his own user name. This is more or lesswhat the SQL standard wants anyway (plus "implementation-defined")Hide information_schema.user_mapping_options.option_value, unless the currentuser is the one associated with the user mapping, or is the server owner andthe mapping is for PUBLIC, or is a superuser. This is to protect passwords.Also, fix a bug in information_schema._pg_foreign_servers, which hid serversusing wrappers where the current user did not have privileges on the wrapper.The correct behavior is to hide servers where the current user has noprivileges on the server.