From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: pg_dump: provide a stable sort order for rules. |
Date: | 2024-11-04 18:31:19 |
Message-ID: | E1t81rD-000BHA-9U@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
pg_dump: provide a stable sort order for rules.
Previously, we sorted rules by schema name and then rule name;
if that wasn't unique, we sorted by rule OID. This can be
problematic for comparing dumps from databases with different
histories, especially since certain rule names like "_RETURN"
are very common. Let's make the sort key schema name, rule name,
table name, which should be unique. (This is the same behavior
we've long used for triggers and RLS policies.)
Andreas Karlsson
Discussion: https://postgr.es/m/b4e468d8-0cd6-42e6-ac8a-1d6afa6e0cf1@proxel.se
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/350e6b8ea86c22c0b95c2e32a4e8d109255b5596
Modified Files
--------------
src/bin/pg_dump/pg_dump_sort.c | 11 +++++++++++
1 file changed, 11 insertions(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2024-11-04 19:04:25 | Re: pgsql: Implement pg_wal_replay_wait() stored procedure |
Previous Message | Masahiko Sawada | 2024-11-04 18:22:12 | pgsql: Fix typo in comment of gistdoinsert(). |