Re: Segmentation fault in pg_dumpall from master down to 9.1 and other bug introduced by RLS - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Segmentation fault in pg_dumpall from master down to 9.1 and other bug introduced by RLS
Date
Msg-id CA+TgmobB4thgOU-1JKMwZPoSx7j0hgDPddR_3N1PR4URmRaYng@mail.gmail.com
Whole thread Raw
In response to Re: Segmentation fault in pg_dumpall from master down to 9.1 and other bug introduced by RLS  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Fri, Nov 14, 2014 at 2:51 PM, Stephen Frost <sfrost@snowman.net> wrote:
> * Robert Haas (robertmhaas@gmail.com) wrote:
>> On Thu, Nov 13, 2014 at 6:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> > What's bothering me is that I see this in pg_dumpall output from a 9.4
>> > or earlier database:
>> >
>> > ALTER ROLE postgres WITH SUPERUSER INHERIT CREATEROLE CREATEDB LOGIN REPLICATION NOBYPASSRLS;
>>
>> What about leaving out NOBYPASSRLS and letting it go to whatever the default is?
>
> I'd be fine with that- but would we want to do it for the other role
> attributes also?  Specifically rolcreaterole and rolreplication for
> older server versions.  I'm still of the opinion that we should just
> drop the explicit "true" for all the role attributes for the bootstrap
> superuser and then go with this suggestion to let it go to the default
> for upgrades from older versions.

Not sure; I was just brainstorming.

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



pgsql-hackers by date:

Previous
From: Alex Shulgin
Date:
Subject: Re: Idle transaction cancel/timeout and SSL revisited
Next
From: Stephen Frost
Date:
Subject: Re: On the warpath again about ill-considered inclusion nests