| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Casey Allen Shobe <cshobe(at)secureworks(dot)net> |
| Cc: | 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:11:04 |
| Message-ID: | 1032099066.19130.4.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-novice |
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.
--
Rod Taylor
| From | Date | Subject | |
|---|---|---|---|
| Next Message | botik32 | 2002-09-15 14:11:14 | Memory leak in client application |
| Previous Message | Casey Allen Shobe | 2002-09-15 12:17:18 | Referencing a superselect's column by it's declared alias from a subselect fails |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Casey Allen Shobe | 2002-09-15 14:16:23 | Re: Postgres storing time in strange manner |
| Previous Message | Casey Allen Shobe | 2002-09-15 12:32:57 | RESOLVED: Deep quotation |