From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Arthur Zakirov <zaartur(at)gmail(dot)com> |
Cc: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_upgrade fails with non-standard ACL |
Date: | 2019-12-04 08:15:56 |
Message-ID: | 20191204081556.GA99403@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 04, 2019 at 12:17:25PM +0900, Arthur Zakirov wrote:
> I updated the patch. It generates "revoke_objects.sql" (similar to v3 patch)
> now and doesn't rely on --check option. It also logs still FATAL message
> because it seems pg_upgrade should stop here since it fails later if there
> are objects with changed identities.
(I haven't looked at the patch yet, sorry!)
FWIW, I am not much a fan of that part because the output generated by
the description is most likely not compatible with the grammar
supported.
In order to make the review easier, and to test for all the patterns
we need to cover, I have an evil idea though. Could you write a
dummy, still simple patch for HEAD which introduces
backward-incompatible changes for all the object types we want to
stress? Then by having ACLs on the source server which are fakely
broken on the target server we can make sure that the queries we have
are right, and that they report the objects we are looking for.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-12-04 08:20:49 | Re: Update minimum SSL version |
Previous Message | Peter Eisentraut | 2019-12-04 08:10:04 | Re: Update minimum SSL version |