Re: Integer datetimes - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: Integer datetimes
Date
Msg-id 47E381A2.2070905@sun.com
Whole thread Raw
In response to Re: Integer datetimes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Integer datetimes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane napsal(a):
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> Neil Conway wrote:
>>> Sure -- I sent in a patch earlier, but I'll post an updated version
>>> shortly.
> 
>> Hmm, I mean just switching the default value in configure.in ... is
>> there anything else that needs doing at this point?
> 
> Well, that's hardly a one-liner.  If nothing else there are probably
> multiple places in the documentation that need adjustment.
> 

Does we keep same OID for this type? I prefer to redefine it as new type. It 
helps to determine which type is it for upgrade purpose. I think best solution 
is to have both code floating/int active and configure or initdb only perform 
correct linking in BKI file to preferred variant.

The result will be two datatypes datetime and timestamp_int or timestamp_float.
Or maybe better is to have two datatypes timestamp_int timestamp_float and one 
domain timestamp which points to preferred type.

    Zdenek


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Commit Fest (was Re: Sort Refinement)
Next
From: Gregory Stark
Date:
Subject: Re: Commit Fest