Re: Top five challenges

From: silly sad <sad(at)bestmx(dot)ru>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Top five challenges
Date: 2011-03-10 16:45:44
Message-ID: 4D790038.4050700@bestmx.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-www

On 03/10/11 19:01, Bruce Momjian wrote:
> 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.
>
> And we document why the default is so odd:
>
> http://www.postgresql.org/docs/9.0/static/datatype-datetime.html#DATATYPE-TIMEZONES
>
> Note: The SQL standard requires that writing just timestamp be
> equivalent to timestamp without time zone, and PostgreSQL honors that
> behavior. (Releases prior to 7.3 treated it as timestamp with time
> zone.)

do you document why 'epoch'::timestamp is not the true 'epoch' unless
timezone is not GMT?

if you mention any timestamp except 'epoch' it will be interpreted
correctly taking in account timezone setting.

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message silly sad 2011-03-10 16:53:55 Re: Top five challenges
Previous Message Bruce Momjian 2011-03-10 16:45:02 Re: Top five challenges

Browse pgsql-www by date

  From Date Subject
Next Message silly sad 2011-03-10 16:53:55 Re: Top five challenges
Previous Message Bruce Momjian 2011-03-10 16:45:02 Re: Top five challenges