| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] postgres_fdw super user checks |
| Date: | 2017-11-29 14:12:37 |
| Message-ID: | 20171129141237.GF4628@tamriel.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ashutosh,
* Ashutosh Bapat (ashutosh(dot)bapat(at)enterprisedb(dot)com) wrote:
> On Wed, Nov 29, 2017 at 4:56 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > The "global rethink" being contemplated seems to be more about
> > authentication forwarding than it is about this specific change. If
> > there's some 'global rethink' which is actually applicable to this
> > specific deviation from the usual "use the view's owner for privilege
> > checks", then it's unclear to me what that is.
>
> Global rethink may constitute other authentication methods like
> certificate based authentication. But I am not clear about global
> rethink in the context of owner privileges problem being discussed
> here.
Right, I'm all for an independent discussion about how we can have
same-cluster or cross-cluster trust relationships set up to make it
easier for users in one cluster/database to access tables in another
that they should be allowed to, but that's a different topic from this.
In other words, I think we're agreeing here. :)
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-11-29 14:15:21 | Re: PATCH: pgbench - option to build using ppoll() for larger connection counts |
| Previous Message | Simon Riggs | 2017-11-29 14:05:35 | Re: [HACKERS] GUC for cleanup indexes threshold. |