From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Integer datetimes |
Date: | 2008-03-24 21:19:45 |
Message-ID: | 47E81AF1.5030701@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane napsal(a):
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
>> The result will be two datatypes datetime and timestamp_int or timestamp_float.
>
> This is not happening, at least not without 100 times more work than
> anyone has shown willingness to put into the issue. It seems fairly
> clear that everyone thinks the int64 datatypes will be the mainstream
> usage, and the float implementation will be interesting only on very
> old platforms or for very specialized applications. I cannot see us
> putting in the effort needed to refactor the code as two
> simultaneously-available datatypes.
I understand your arguments, but it is important for in-place upgrade. If you
will start new postgreSQL on e.g 8.3 database cluster, you need method how to
process floating point timestamp. Minimal we need to have cast from floating
point timestamp to integer timestamp. I put it on my ToDo with low priority.
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-03-24 21:24:28 | Re: New email list for emergency communications |
Previous Message | Devrim GÜNDÜZ | 2008-03-24 21:17:15 | Re: New email list for emergency communications |