public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Jeff Janes <[email protected]>
Cc: [email protected]
Subject: Re: document effect of USAGE on foreign server to dblink
Date: Mon, 23 Dec 2019 17:48:37 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMkU=1xu5HKH46UFYda7xi8xTOzm7_GTTBTJ9r=_CbPq-N5qkw@mail.gmail.com>
References: <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com>
	<[email protected]>
	<CAMkU=1xu5HKH46UFYda7xi8xTOzm7_GTTBTJ9r=_CbPq-N5qkw@mail.gmail.com>

On Thu, Dec 19, 2019 at 03:54:44PM -0500, Jeff Janes wrote:
> 
> 
> On Thu, Dec 19, 2019 at 11:43 AM Bruce Momjian <[email protected]> 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  <[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)

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