Skip site navigation (1) Skip section navigation (2)

Re: Top five challenges

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: silly sad <sad(at)bestmx(dot)ru>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Top five challenges
Date: 2011-03-10 17:07:09
Message-ID: 4D79053D.1050309@gmail.com (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-www
On 03/10/2011 08:53 AM, silly sad wrote:


>>
>> Well, 'epoch' clearly is a point in time with the hour being midnight at
>> GMT, so I don't see a problem with epoch making such an adjustment:
>
>
> great! the flexible epoch!
>
> when do want to point an epoch to?
> just set timezone and enjoy.
>

I am not sure what your point is. The epoch being used is just one of 
many that could have been used, see link below. So by definition the 
term epoch is flexible. The Postgres project has chosen a particular 
value for 'epoch' as explained in the docs. This 'epoch' is a special 
datetime value pinned to a point in time(as Bruce mentioned). All adding 
a time zone does is translate the GMT point in time to the time zone 
point in time. They are the same time.

http://en.wikipedia.org/wiki/Epoch_%28reference_date%29#Computing


-- 
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

pgsql-www by date

Next:From: silly sadDate: 2011-03-10 17:15:34
Subject: Re: Top five challenges
Previous:From: Bruce MomjianDate: 2011-03-10 17:00:08
Subject: Re: Read uncommitted ever possible?

pgsql-advocacy by date

Next:From: silly sadDate: 2011-03-10 17:15:34
Subject: Re: Top five challenges
Previous:From: silly sadDate: 2011-03-10 16:53:55
Subject: Re: Top five challenges

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group