> Right. But the problem with switching the OID default is not a matter
> of code --- it's of working out what the compatibility issues are.
> As I recall, one thing people did not want was for pg_dump to plaster
> WITH OIDS or WITHOUT OIDS on every single CREATE TABLE, as this would
> pretty much destroy any shot at loading PG dumps into any other
> database.
Ummm...what about SERIAL columns, ALTER TABLE / SET STATS, SET STORAGE,
custom types, 'btree' in CREATE INDEX, SET SEARCH_PATH, '::" cast operator,
stored procedures, rules, etc. - how is adding WITH OIDS going to change
that?!
> What we need is an agreement on the behavior we want (making
> the best possible compromise between this and other compatibility
> desires). After that, the actual patch is probably trivial, while in
> advance of some consensus on the behavior, offering a patch is a waste
> of time.
Sure.
Chris
