"PostgreSQL Bugs List" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
