On Wed, Sep 22, 2010 at 9:00 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Technically, there's no reason why we can't do this for 9.1. What we
>> can do is change the name of the "time with timezone" type to
>> something like "oldtimetz", keeping the current OID. And then we can
>> add a new type called "time with timezone". [ with large amounts of
>> consequent work ]
>
> I think you missed the point of my response, which is that there are
> easily 10^6 more-pressing things to work on than the size of timetz.
> Do you know of any actual use cases for it?
Well, I wasn't responding to you - I was responding to Josh.
Regardless of the merits of redesigning this particular data type, I
think it's important for us to cultivate a mindset of figuring out how
we can make gradual improvements to the on-disk format without
earth-shattering consequences for pg_upgrade. Mind you, I don't
currently have the time to hack on this for, uh, more or less the
reason you state. But if my boss told me he double my pay if I got it
done, I wouldn't tell him it's technically impossible.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company