Re: [RFC] Removing "magic" oids
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Date: 2018-11-22T21:14:52Z
Lists: pgsql-hackers
Hi, On 2018-11-21 23:32:07 -0500, Andrew Dunstan wrote: > On 11/21/18 7:14 PM, Andres Freund wrote: > > Could you check whether you > > still encounter the issue after applying the attached fix? > > > > > This has largely fixed the problem, so I think this should be applied. Cool, will do so tomorrow or such. Thanks for testing. > With some adjustments to the tests to remove problematic cases (e.g. > postgres_fdw's ft_pg_type) the tests pass. The exception is > HEAD->HEAD. The change is that the LOs are not dumped in the same > order pre and post upgrade. I can change the tests to allow for a > greater fuzz factor - generally when the source and target are the > same we don't allow any fuzz. Or if we care we could do a better job > of dumping LOs in a consistent order. So you'd want to dump large objects in oid order or such? Probably comparatively not a huge overhead, but also not nothing? We don't really force ordering in other places in pg_dump afaik. Greetings, Andres Freund
Commits
-
Revive test of concurrent OID generation.
- dffb891d78cb 12.0 landed
- 8a0cbb88524e 13.0 landed
-
Fix typo introduced in 578b229718.
- 54bb22f66af9 12.0 landed
-
Fix pg_upgrade for oid removal.
- 12a53c732ced 12.0 landed
-
Fix sepgsql compile error caused by oid removal.
- 937e4e509998 12.0 landed
-
Remove WITH OIDS support, change oid catalog column visibility.
- 578b229718e8 12.0 landed