Re: to_timestamp error handling.

Greg Stark <stark(at)enterprisedb(dot)com> writes:
> On Wed, Jun 10, 2009 at 3:23 PM, Dhaval
> Jaiswal<dhaval(dot)jaiswal(at)enterprisedb(dot)com> wrote:
>> postgres=# select to_timestamp('20096010','YYYYMMDD');
>> ---------------------------
>> 2013-12-18 00:00:00+05:30

> I suspect you'll find that the 60th month after the start of 2009 is
> in fact december 2013.

Yeah. I was kind of surprised that CVS HEAD doesn't complain about this
--- I thought we'd tightened up the error checking in to_timestamp.

I think it's been occasionally seen as a feature that something like
'2009-02-29' will be read as '2009-03-01', but it's hard to imagine a
real use case for month outside 1-12.

regards, tom lane