Re: BUG #1180: incorrect date handling - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1180: incorrect date handling
Date
Msg-id 26097.1087961141@sss.pgh.pa.us
Whole thread Raw
In response to BUG #1180: incorrect date handling  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
Responses Re: BUG #1180: incorrect date handling
List pgsql-bugs
"PostgreSQL Bugs List" <pgsql-bugs@postgresql.org> writes:
> PostgreSQL version: 7.3.2

> colony=# insert into foo values ('2003-12-11 23:59:60.00');
> ERROR:  Bad timestamp external representation '2003-12-11 23:59:60.00'

Use a more recent PG version ... we have fixed a thing or two since
7.3 (in fact 7.3.3 and later versions take this, if I read the CVS logs
aright).

> under 7.4.2, (had a friend test it out) inserting a timestamp with a time of
> 23:59:60.00 is allowed, it just increments the day and sets the time to
> 00:00:00 (as one would expect). However it still allows you to insert the
> time as `23:59:59.9999999` and it updates the time (incorrectly) to
> `23:59:60.00` instead of incrementing the day and setting the time to
> 00:00:00 (since 23:59:60 is .. or should be invalid).

Horsepucky.

regression=# select version();
                            version
---------------------------------------------------------------
 PostgreSQL 7.4.3 on hppa-hp-hpux10.20, compiled by GCC 2.95.3
(1 row)

regression=# select '2003-12-11 23:59:60.00'::timestamp;
      timestamp
---------------------
 2003-12-12 00:00:00
(1 row)

            regards, tom lane

pgsql-bugs by date:

Previous
From: "PostgreSQL Bugs List"
Date:
Subject: BUG #1180: incorrect date handling
Next
From: Stephan Szabo
Date:
Subject: Re: BUG #1180: incorrect date handling