Stephen Frost <sfr...@snowman.net> writes:
> Let's create a new data type for this which supports old and new types,
> add what casts make sense, and call it a day. Changing the data type
> name out from under people is not helping anyone.
+1. I do not think changing behavior for the existing type name is
going to be a net win. If we'd been smart enough to make the type
varlena from the get-go, maybe we could get away with it, but there
is just way too much risk of trouble with a change in a fixed-length
type's on-the-wire representation.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
