From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Segmentation fault in pg_dumpall from master down to 9.1 and other bug introduced by RLS |
Date: | 2014-11-14 01:24:36 |
Message-ID: | 20141114012436.GL28859@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)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;
Ah, yeah, good point.
> That means that if you do a pg_upgrade from a 9.4 database, your built-in
> superuser will now not have rolbypassrls set, though it does in a database
> built in any other way. Even if that doesn't have any functional effect,
> it's a recipe for confusion IMO. So I think that the code ought to be
> "usesuper as rolbypassrls" rather than "false as rolbypassrls" for
> back branches.
>
> The only other similar case is rolreplication, which perhaps also ought
> to read as usesuper for old branches.
Agreed. I'll take care of both and we'll make sure the new role
attributes being added will do the same for upgrades also.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2014-11-14 01:25:21 | Re: Using 128-bit integers for sum, avg and statistics aggregates |
Previous Message | Kouhei Kaigai | 2014-11-14 01:12:45 | Re: using custom scan nodes to prototype parallel sequential scan |