-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Apr 26, 2008 at 6:02 AM, Tom Lane wrote: > "Brendan Jurd" writes: > > Has anyone had a close look at how hard it would be allow just the > > "add to the end" capability? > > The problem is you can't guarantee anything about the ordering of the > new value relative to the old ones. The OID it's assigned might be > after them, or before them if the OID counter has wrapped around, > or (with much smaller probability) between two existing ones. >
I see. So to add a value on to the end with guaranteed ordering, you would have to rebuild the enum from scratch anyway. Then there's no technical difference at all in implementing "add to the end" and "add/remove". Thanks for the answer. Cheers, BJ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: http://getfiregpg.org iD8DBQFIEjrO5YBsbHkuyV0RAogmAKC3u8wogvrUNSfFUx/PbKyS6U2/DgCgjDSu z+VNazq7LiRdiU4oUvKL0jc= =obXq -----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
