From: | silly sad <sad(at)bestmx(dot)ru> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Top five challenges |
Date: | 2011-03-03 11:01:21 |
Message-ID: | 4D6F7501.30904@bestmx.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-www |
On 03/02/11 17:07, Alvaro Herrera wrote:
> Excerpts from sad's message of mié mar 02 10:23:53 -0300 2011:
>> On Mar 2 2011, Josh Berkus wrote:
>
>>>> 3. To make TIMESTAMPTZ useful by introducing proper type cast
>>>> TIMESTAMPTZ to TIMESTAMP
>>>
>>> Why are you using Timestamp-no-tz at all? I was thinking we should
>>> change the default ...
>>
>> Why did u introduced it?
>
> The standard requires the current behavior. It's not going to change.
> It changed in 7.1 or so.
>
does standard require to have TWO DIFFERENT EPOCHS?
SELECT 'epoch'::TIMESTAMPTZ, 'epoch'::TIMESTAMP;
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-03-03 17:58:44 | Re: Top five challenges |
Previous Message | Magnus Hagander | 2011-03-02 16:36:00 | Re: Top five challenges |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-03-03 17:58:44 | Re: Top five challenges |
Previous Message | Magnus Hagander | 2011-03-02 16:36:00 | Re: Top five challenges |