Re: SET ROLE and reserved roles

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET ROLE and reserved roles
Date: 2016-04-27 02:20:31
Message-ID: 20160427022031.GA638386@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> On Mon, Apr 25, 2016 at 6:55 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:

> > Working up a patch to remove these checks should be pretty quickly done
> > (iirc, I've actually got an independent patch around from when I added
> > them, just need to find it and then go through the committed patches to
> > make sure I take care of everything), but would like to make sure that
> > we're now all on the same page and that *all* of these checks should be
> > removed, making default roles just exactly like "regular" roles, except
> > that they're created at initdb time and have "special" rights provided
> > by C-level code checks.
>
> That's what I'm thinking. I would welcome other views.

I agree with that view, assuming pg_dump correctly produces GRANTs to
replicate what was done in a database regarding those roles (and same
with pg_dumpall -g). I think it already works that way, but I may be
mistaken.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-04-27 02:23:04 Re: Removing faulty hyperLogLog merge function
Previous Message Noah Misch 2016-04-27 02:04:33 Re: xlc atomics