- Notifications
You must be signed in to change notification settings - Fork5.2k
Commit9affed2
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 beproblematic for comparing dumps from databases with differenthistories, 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 behaviorwe've long used for triggers and RLS policies.)Andreas KarlssonThis back-patches v18 commit350e6b8 toall supported branches. The next commit will assert that pg_dumpprovides a stable sort order for all object types. That assertion wouldfail without stabilizing DO_RULE order as this commit did.Discussion:https://postgr.es/m/b4e468d8-0cd6-42e6-ac8a-1d6afa6e0cf1@proxel.seDiscussion:https://postgr.es/m/20250707192654.9e.nmisch@google.comBackpatch-through: 13-171 parentc1984be commit9affed2
1 file changed
+11
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
291 | 291 | | |
292 | 292 | | |
293 | 293 | | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
| 300 | + | |
| 301 | + | |
| 302 | + | |
| 303 | + | |
| 304 | + | |
294 | 305 | | |
295 | 306 | | |
296 | 307 | | |
| |||
0 commit comments
Comments
(0)