public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Jeff Janes <[email protected]>
Cc: [email protected]
Subject: Re: document effect of USAGE on foreign server to dblink
Date: Thu, 19 Dec 2019 11:43:14 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com>
References: <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com>
On Wed, Nov 27, 2019 at 11:33:03AM -0500, Jeff Janes wrote:
> I think that the permissions around the usage of foreign server names as
> connection names in dblink should be documented, as in the attached.
Uh, this looks like an odd place to document it, since this part is
talking about permissions.
> 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?
I have no idea.
---------------------------------------------------------------------------
>
> Cheers,
>
> Jeff
> 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>
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
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], [email protected]
Subject: Re: document effect of USAGE on foreign server to dblink
In-Reply-To: <[email protected]>
* 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