Re: Always have pg_dump write rules in a consistent order
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Karlsson <andreas@proxel.se>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-11-04T18:32:53Z
Lists: pgsql-hackers
Andreas Karlsson <andreas@proxel.se> writes: > When working on a new feature for PostgreSQL I noticed that the > pg_upgrade tests became flaky due to rules being dumped in a different > order between the original cluster and the upgraded cluster. (For > context: my regress scripts left a bunch of views with dependency > circles which I had forgot to clean up.) > So I propose that we sort rules on (schema, name, relation_name) instead > of (schema, name, oid) like it currently does. The patch itself is small > enough and makes it easier to test that we upgrade rules and views > correctly with pg_upgrade. Seems reasonable. Pushed with some trivial cosmetic adjustments to make it look more like the identical adjacent cases for policies and triggers. regards, tom lane
Commits
-
pg_dump: provide a stable sort order for rules.
- cc9a62c51a18 13.22 landed
- 25388fb2cb84 14.19 landed
- e99010cbd8e2 15.14 landed
- 9affed26349a 16.10 landed
- 5dd4957b28df 17.6 landed
- 350e6b8ea86c 18.0 landed