Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVgwl-0006Xk-7M for pgsql-docs@arkaria.postgresql.org; Fri, 15 Nov 2019 19:07:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iVgwk-0002zl-1y for pgsql-docs@arkaria.postgresql.org; Fri, 15 Nov 2019 19:07:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVgth-0007WT-6S for pgsql-docs@lists.postgresql.org; Fri, 15 Nov 2019 19:04:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVgta-0004mn-3s for pgsql-docs@lists.postgresql.org; Fri, 15 Nov 2019 19:04:44 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xAFJ4abQ011508; Fri, 15 Nov 2019 14:04:36 -0500 From: Tom Lane To: joe@nahmias.net cc: pgsql-docs@lists.postgresql.org Subject: Re: no mention of GRANT USAGE in postgres_fdw docs In-reply-to: <157377058468.1209.1912214624357780577@wrigleys.postgresql.org> References: <157377058468.1209.1912214624357780577@wrigleys.postgresql.org> Comments: In-reply-to PG Doc comments form message dated "Thu, 14 Nov 2019 22:29:44 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11506.1573844676.1@sss.pgh.pa.us> Date: Fri, 15 Nov 2019 14:04:36 -0500 Message-ID: <11507.1573844676@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Doc comments form writes: > The documentation page for postgres_fdw > gives a nice > step by step on what's needed to configure a FOREIGN SERVER. However, one > crucial step is missed, and that is that you need to issue GRANT USAGE ON > FOREIGN SERVER before you can successfully run step 4, IMPORT FOREIGN > SCHEMA. That paragraph links to the IMPORT FOREIGN SCHEMA reference page, which says To use IMPORT FOREIGN SCHEMA, the user must have USAGE privilege on the foreign server, as well as CREATE privilege on the target schema. 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. Is there some reason why this was particularly hard to discover? I'd have expected that you got a reasonably clear permissions- failure error from the IMPORT. If you didn't, maybe there's an opportunity to improve that. regards, tom lane