-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Apr 26, 2008 at 6:19 AM, Tom Dunstan wrote: > I wonder if it's worth revisiting the decision to save enums on disk > as oids. The very first idea that I had was to have an enum value as > the combination of both an enum id and the ordinal value.
That's very intuitive. > The nice thing about the above approach is that we could space out the > ordinal values so as to allow people to insert a fair number of extra > values before forcing a rewrite of the table. The only thing we really > couldn't handle that way would be reordering - we'd need an extra > layer of indirection for that, which would have some performance > penalties. None of the standard operators for enums require a syscache > lookup currently, only I/O does, > Wouldn't you still be able to do a reorder with a table rewrite? Cheers, BJ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIEkBC5YBsbHkuyV0RAggsAJ0btEoQTTwiakLPRg/sixcXFCroLwCgleri Q/JebP+AWErEl+w2+QHL16o= =YUGG -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
