Oh! I didn't know that was possible! And then I looked in the documentation and there it was, very clearly explained. (That doesn't surprise me at all; I've always appreciated how clear and thorough the Postgres documentation is.) That will work beautifully for us; thanks again for your help. I promise to scour the documentation more carefully before I bug the mailing list next time. :)
Thanks,
Natalie
> On Jul 17, 2015, at 12:59 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
>
> Natalie Wenz <nataliewenz@xxxxxxxxxxx> writes:
>> Oh! Of course! The local database doesn't know anything about the role privileges on the remote database, so the information isn't even available on the local database to somehow take the union of all the privileges of foo and bar because they are defined on the remote database. Thanks for responding. I got so wrapped up in our simple use case (where any individual_user in the local_group would connect to foreign_server as the same foreign_user) and couldn't come up with a counter example.
>
>> For our use case, can you think of any other way to do it besides creating a user mapping for every member of local_group? Gilberto's suggestion of setting the session authorization (I think?) won't work because the individual_users don't have privileges to set that. ("ERROR: permission denied to set session authorization")
>
> Would it work for them to do SET ROLE to the group whose mapping they want
> to use? IIRC that's allowed for any member of the group. The problem
> with this is that their privileges for local operations are also affected,
> so maybe that doesn't help you.
>
> regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
