From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15788: 'pg_dump --create' orders database GRANTs incorrectly |
Date: | 2019-05-22 16:59:53 |
Message-ID: | 1FE3AB7F-0AF9-4F38-B41D-51F219509281@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 5/21/19, 11:26 PM, "Michael Paquier" <michael(at)paquier(dot)xyz> wrote:
> On Mon, May 20, 2019 at 10:37:50PM +0000, Bossart, Nathan wrote:
>> On 5/20/19, 1:27 AM, "Michael Paquier" <michael(at)paquier(dot)xyz> wrote:
>>> I had first a hard time parsing the subqueries added, so I have
>>> tweaked your patch with more indentation, and a comment block with
>>> more details about why we need to preserve the ACL ordering (you will
>>> note that I don't have a lot of imagination here).
>>
>> Thanks. Your version looks good to me.
>
> Okay, I have done more tests, checks and tweaks on this stuff, and
> pushed the fix for databases down to 9.6.
Thanks!
> The problem comes from dumpTablespaces() which still has a broken ACL
> ordering logic. I'll start a new thread about that as this thread is
> actually now fixed. It would be interesting to refactor all that
> stuff, but I'd like to think that it would be much more interesting if
> we could get pg_init_privs to work with databases and tablespace
> instead, but that would not be back-patchable. So I'll focus on the
> bug fix.
I'll take a look at this.
Nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2019-05-23 13:16:03 | Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault |
Previous Message | Michael Paquier | 2019-05-22 06:26:26 | Re: BUG #15788: 'pg_dump --create' orders database GRANTs incorrectly |