forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit471a7af
committed
Ensure consistent sort order of large objects in pg_dump.
The primary purpose of this commit is to ensure pg_upgrade tests yieldcomparable dumps pre/post upgrade, which got broken by12a53c7 /578b229, as the order in pg_largeobject_metadata is likely todiffer pre/post upgrade.It also seems like a generally good idea to make sure such dumps arecomparable, outside of pg_upgrade tests.LO metadata already was already dumped in an ordered manner as themetadata is dumped in a well defined order viasortDumpableObjectsByTypeName() and sortDumpableObjects(). But largeobject data is currently not tracked via that mechanism.As Tom points out it seems possible that at some point dumpBlobs() wasassumed to dump out objects in a well defined order, due to the use ofDISTINCT, which at that time only was done using sorting.Per complaint from Andrew Dunstan and discussion with him and TomLane.Author: Andres FreundDiscussion:https://postgr.es/m/2735.1543333649@sss.pgh.pa.us1 parentb238527 commit471a7af
1 file changed
+6
-2
lines changedLines changed: 6 additions & 2 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
3328 | 3328 |
| |
3329 | 3329 |
| |
3330 | 3330 |
| |
3331 |
| - | |
| 3331 | + | |
| 3332 | + | |
| 3333 | + | |
3332 | 3334 |
| |
3333 |
| - | |
| 3335 | + | |
| 3336 | + | |
| 3337 | + | |
3334 | 3338 |
| |
3335 | 3339 |
| |
3336 | 3340 |
| |
|
0 commit comments
Comments
(0)