From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
---|---|
To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Test instability when pg_dump orders by OID |
Date: | 2025-08-10 11:41:20 |
Message-ID: | CALdSSPhZyLua3Vz2Ug8VOASbhP41h-7784MT8s9_+90eE06Aaw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all!
On Sun, 10 Aug 2025 at 12:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>
> Hello Noah,
>
> 04.08.2025 03:03, Noah Misch wrote:
> > Pushed as 0decd5e. ...
>
> Please look at a new anomaly introduced with that commit. The following
> script:
> createdb regression
>
> echo "
> CREATE USER u1;
> ALTER DEFAULT PRIVILEGES FOR ROLE u1 REVOKE INSERT ON TABLES FROM u1;
>
> CREATE USER u2;
> ALTER DEFAULT PRIVILEGES FOR ROLE u2 REVOKE INSERT ON TABLES FROM u2;
> " | psql regression
>
> pg_dump regression
>
> triggers:
> pg_dump: pg_dump_sort.c:454: DOTypeNameCompare: Assertion `0' failed.
I reproduced this. Indeed, in case of default acl we happen to use OID sort.
PFA resolves this issue. I simply added DEFAULT ACL case-specific
tiebreaker that resolves object order.
--
Best regards,
Kirill Reshke
Attachment | Content-Type | Size |
---|---|---|
0001-Handle-DEFAULT-ACL-case-in-DOTypeNameCompare-functio.patch | application/octet-stream | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2025-08-10 15:20:12 | Re: Emitting JSON to file using COPY TO |
Previous Message | Jingtang Zhang | 2025-08-10 10:53:19 | Possible inaccurate description of wal_compression in docs |