Обсуждение: document effect of USAGE on foreign server to dblink
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
Вложения
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 <bruce@momjian.us> 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 +
On Thu, Dec 19, 2019 at 11:43 AM Bruce Momjian <bruce@momjian.us> wrote:
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.
Yes, giving this permission gives you usage of it in a place that is non-obvious, and that the doc doesn't mention. Isn't the place about permission the correct place to document these non-obvious permissions?
Cheers,
Jeff
On Thu, Dec 19, 2019 at 03:54:44PM -0500, Jeff Janes wrote: > > > On Thu, Dec 19, 2019 at 11:43 AM Bruce Momjian <bruce@momjian.us> wrote: > > 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. > > > Yes, giving this permission gives you usage of it in a place that is > non-obvious, and that the doc doesn't mention. Isn't the place about > permission the correct place to document these non-obvious permissions? How is using a foreign server name in dblink a permission? -- Bruce Momjian <bruce@momjian.us> 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 +