Allow FDW user mapping against roles about crate HOT 3 CLOSED

Is something like this supported in PostgreSQL?

A user can be granted more than one role which means there would need to be some rules in regards to which mapping takes precedence.

Potential workaround:

• Create one user for fdw
• Create views with that user that re-expose the foreign tables
• Give other users privileges on the views

from crate.

Is something like this supported in PostgreSQL?

No, PostgreSQL allows the following:

CREATE USER MAPPING [ IF NOT EXISTS ] FOR { user_name | USER | CURRENT_ROLE | CURRENT_USER | PUBLIC }

where USER | CURRENT_ROLE | CURRENT_USER are equal to the current user, while PUBLIC specifies a user mapping to be used when there is no user-specific mapping is applicable.

• This also is followed by e.g. DB2 and Greenplum.
• SQL Server is using Linked Servers and also either allows NULL (which is equivalent to PUBLIC) or a specific user.

I would tend to allow CREATE USER MAPPING FOR PUBLIC and control access to foreign tables via user privileges and/or use a VIEW as described above -> #16166

from crate.

Closing in favour of #16166

from crate.