Karel Zak <[EMAIL PROTECTED]> writes:
> The to_timestamp() do nothing with date/time and use internal
> tm2timestamp() routine only. I don't think that check all date/time
> ranges in to_timestamp() is good idea if it's already implemented at
> the another place in our code.
But it evidently *isn't* checked. As of CVS tip:
regression=# select to_timestamp('44 October 2003', 'DD FMMonth YYYY');
to_timestamp
------------------------
2003-11-13 00:00:00-05
(1 row)
The regular timestamp input converter certainly has the checks:
regression=# select '44 October 2003'::timestamp;
ERROR: invalid input syntax for type timestamp: "44 October 2003"
but evidently those checks are not in whatever code path to_timestamp
is calling.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
