public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: David G. Johnston <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: no mention of GRANT USAGE in postgres_fdw docs
Date: Fri, 15 Nov 2019 14:50:41 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwbLyaAv8i9q_82kD+UNCet4emWgOy2PiQ8LT6Ld7r+KWg@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CAKFQuwbLyaAv8i9q_82kD+UNCet4emWgOy2PiQ8LT6Ld7r+KWg@mail.gmail.com>

"David G. Johnston" <[email protected]> writes:
> On Fri, Nov 15, 2019 at 12:05 PM Tom Lane <[email protected]> wrote:
>> I'm not clear why we should duplicate that information here, especially
>> when we're not duplicating any of the other essential information about
>> how to use IMPORT FOREIGN SCHEMA.  Nor does this summary mention the
>> privilege requirements for any of the other commands it suggests using.

> The overview page says: "Create a user mapping, using CREATE USER MAPPING,
> for each database user you want to allow to access each foreign server."
> It seems reasonable to add that you need to grant those same users the
> USAGE privilege on each foreign server as well.

But you don't necessarily, do you?  I think you only need that to
create a foreign table referencing the server, not to use one that
somebody else created.  (Too lazy to check the details right now.)

Anyway, my point is that details like this belong in the respective
command man pages.  If we were to copy them into postgres-fdw's
summary, we'd never remember to update that if they changed.

			regards, tom lane

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], [email protected], [email protected]
  Subject: Re: no mention of GRANT USAGE in postgres_fdw docs
  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