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

Re: Postgres storing time in strange manner

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Casey Allen Shobe <cshobe(at)secureworks(dot)net>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, pgsql-bugs(at)postgresql(dot)org,pgsql-novice(at)postgresql(dot)org
Subject: Re: Postgres storing time in strange manner
Date: 2002-09-15 14:32:35
Message-ID: 28541.1032100355@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-novice
> On Sunday 15 September 2002 10:11 am, Rod Taylor wrote:
>> On Sun, 2002-09-15 at 03:57, Casey Allen Shobe wrote:
>>> I don't have a clue why it's doing this - has anyone else seen this sort
>>> of behavior, or know why it might be doing it?  It shows times wrong, for
>>> instance, it shows 00:04:60 where it should show 00:05:00.  See below:
>> 
>> There are actually 61 seconds in some minutes.  In order to accommodate
>> leap seconds, PostgreSQL allows this to happen -- similarly to how it
>> will also allow 366 days in some years.

True but irrelevant -- PG does not do accounting for leap seconds.

The roundoff bug Casey is looking at is fixed in recent PG versions;
I'd recommend an update to 7.2.2.

			regards, tom lane

In response to

Responses

pgsql-novice by date

Next:From: Rod TaylorDate: 2002-09-15 14:49:22
Subject: Re: Postgres storing time in strange manner
Previous:From: Casey Allen ShobeDate: 2002-09-15 14:16:23
Subject: Re: Postgres storing time in strange manner

pgsql-bugs by date

Next:From: Rod TaylorDate: 2002-09-15 14:49:22
Subject: Re: Postgres storing time in strange manner
Previous:From: Casey Allen ShobeDate: 2002-09-15 14:16:23
Subject: Re: Postgres storing time in strange manner

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