Re: [HACKERS] postgres_fdw super user checks

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] postgres_fdw super user checks
Date: 2017-12-05 16:35:31
Message-ID: CA+TgmoaQ9pwCZfdbvkZwhooNNAuaDJeQBmgmnDvrWbh1fHEPTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 4, 2017 at 5:57 PM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
> I think the real behaviour can be described as something like this:
>
> "Only superusers may connect to foreign servers without password
> authentication, so always specify the <literal>password</literal>
> option for user mappings that may be used by non-superusers." But
> which user mappings may be used by non-superusers can not be defined
> without explaining views owned by superusers. I don't think we should
> be talking about views in that part of documentation.

Well, if we don't, then I'm not sure we can really make this clear.

Anyhow, I've committed the patch to master for now; we can keep
arguing about what, if anything, to do for back-branch documentation.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-12-05 16:41:56 Re: [HACKERS] postgres_fdw super user checks
Previous Message Robert Haas 2017-12-05 15:29:59 Re: [HACKERS] Proposal: Local indexes for partitioned table