Hi again Tom,
I re-read your point 2. “You don't want to grant USAGE on the foreign
server to the localuser, either.” to find out this was exactly the solution
I was looking for. That is: it's fine to not let the basic user create the
foreign tables.
Wow, it was as easy as moving the foreign tabl
On 6/3/20 4:11 AM, Paul Bonaud wrote:
Hi Tom,
Thank you very much for your answer.
I was worried to get this kind of solution, i.e. “don't be so miserly as
not to create a separate one for each privilege level you need.”,
however in the case of a remote database **you have no control over**it
Hi Tom,
Thank you very much for your answer.
I was worried to get this kind of solution, i.e. “don't be so miserly as
not to create a separate one for each privilege level you need.”, however
in the case of a remote database **you have no control over** it sounds
pretty impossible to do.
If I un
Paul Bonaud writes:
> Imagine you have a destination database which you have no control over.
> Let's call it “external-db”. This database has a unique pg user (no
> specific pg permission attributes) with read-write access to the whole
> database let's call it “external-user”.
> ...
> Now over to
Hello,
I couldn't find any answer in the PostgreSQL documentation so here I am
with a question regarding FDW and User Mappings. *Is it possible to define
permissions on user mappings to hide the connection info (mainly the
password) to a user?*
More details of the context:
Imagine you have a
