public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jeff Janes <[email protected]>
To: [email protected]
Subject: document effect of USAGE on foreign server to dblink
Date: Wed, 27 Nov 2019 11:33:03 -0500
Message-ID: <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com> (raw)

I think that the permissions around the usage of foreign server names as
connection names in dblink should be documented, as in the attached.

Also, for dblink itself it says "It is recommended to use the foreign-data
wrapper dblink_fdw when defining the foreign server".  Is there a reason
for this recommendation?  postgres_fdw seems to work fine on the surface,
is there some hidden trap in using it?

Cheers,

Jeff


Attachments:

  [application/octet-stream] server_dblink_priv.patch (608B, 3-server_dblink_priv.patch)
  download | inline diff:
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 0be0774..a171a00 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1829,7 +1829,8 @@ REVOKE ALL ON accounts FROM PUBLIC;
       <para>
        For foreign servers, allows creation of foreign tables using the
        server.  Grantees may also create, alter, or drop their own user
-       mappings associated with that server.
+       mappings associated with that server. Grantees may also use the foreign
+       server as a connection name in <xref linkend="dblink"/>.
       </para>
      </listitem>
     </varlistentry>

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: document effect of USAGE on foreign server to dblink
  In-Reply-To: <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox