Re: [PATCH] Supporting +-Infinity values by to_timestamp(float8) - Mailing list pgsql-hackers

From David Steele
Subject Re: [PATCH] Supporting +-Infinity values by to_timestamp(float8)
Date
Msg-id 56E86264.1000800@pgmasters.net
Whole thread Raw
In response to Re: [PATCH] Supporting +-Infinity values by to_timestamp(float8)  (Vitaly Burovoy <vitaly.burovoy@gmail.com>)
Responses Re: [PATCH] Supporting +-Infinity values by to_timestamp(float8)
Re: [PATCH] Supporting +-Infinity values by to_timestamp(float8)
List pgsql-hackers
On 3/4/16 2:56 PM, Vitaly Burovoy wrote:

> On 3/4/16, Anastasia Lubennikova <a.lubennikova@postgrespro.ru> wrote:
>
>> I think that you should update documentation. At least description of
>> epoch on this page:
>> http://www.postgresql.org/docs/devel/static/functions-datetime.html
> 
> Thank you very much for pointing where it is located (I saw only
> "to_timestamp(TEXT, TEXT)").
> I'll think how to update it.

Vitaly, have you decided how to update this yet?

>> 3. (nitpicking) I don't sure about "4STAMPS" suffix. "4" is nice
>> abbreviation, but it seems slightly confusing to me.
> 
> It doesn't matter for me what it is called, it is short enough and
> reflects a type on which it is applied.
> What would the best name be for it?

Anastasia, any suggestions for a better name, or just leave it as is?

I'm not in favor of the "4", either.  I think I would prefer
JULIAN_MAXYEAR_STAMP.

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: function parse_ident
Next
From: Stephen Frost
Date:
Subject: Re: Default Roles