Re: BUG #9265: why the same interval can't get the same timestamp? - Mailing list pgsql-bugs

From Vik Fearing
Subject Re: BUG #9265: why the same interval can't get the same timestamp?
Date
Msg-id 53036D18.60806@dalibo.com
Whole thread Raw
In response to BUG #9265: why the same interval can't get the same timestamp?  (miaoyimin@huawei.com)
List pgsql-bugs
On 02/18/2014 01:06 PM, miaoyimin@huawei.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      9265
> Logged by:          yimin
> Email address:      miaoyimin@huawei.com
> PostgreSQL version: 9.2.6
> Operating system:   suse 10.3
> Description:
>
> postgres=# select ('epoch'::pg_catalog.timestamptz + 1386201600 * '1
> second'::pg_catalog.interval);
>         ?column?
> ------------------------
>  2013-12-05 08:00:00+08
> (1 row)
>
> postgres=# select ('epoch'::pg_catalog.timestamptz + 16044 * '1
> day'::pg_catalog.interval);
>         ?column?
> ------------------------
>  2013-12-05 07:30:00+08
> (1 row)
>
> postgres=# show timezone;
>      TimeZone
> -------------------
>  Asia/Kuala_Lumpur
> (1 row)
>
>


The timezone changed by thirty minutes on December 31, 1981 so the
number of days since epoch is not the same as the number of seconds.

--
Vik

pgsql-bugs by date:

Previous
From: miaoyimin@huawei.com
Date:
Subject: BUG #9265: why the same interval can't get the same timestamp?
Next
From: Tom Lane
Date:
Subject: Re: BUG #9265: why the same interval can't get the same timestamp?