Date: Mon, 23 Dec 2019 17:48:37 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: document effect of USAGE on foreign server to dblink
Message-ID: <20191223224837.GA24866@momjian.us>
References: 
 <CAMkU=1z7Qky8c0TQ011wPgiriy3qVHVZeOhYgaOccqScRPM19w@mail.gmail.com>
 <20191219164314.GO30116@momjian.us>
 <CAMkU=1xu5HKH46UFYda7xi8xTOzm7_GTTBTJ9r=_CbPq-N5qkw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAMkU=1xu5HKH46UFYda7xi8xTOzm7_GTTBTJ9r=_CbPq-N5qkw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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 +