"Joshua Tolley" <[EMAIL PROTECTED]> writes:
> I'm running this on 8.4devel built from CVS HEAD as of 9:44 AM Moutain
> Daylight time today, on a 32-bit Ubuntu 7.04 box. This is a completely
> new database.
Ugh, apparently there's some state-dependent bug in the recent
to_timestamp fixes:
regression=# \c -
psql (8.4devel)
You are now connected to database "regression".
regression=# select to_timestamp('21-SEP-08 08.15.42.950620 PM', 'DD-MON-YY
HH.MI.SS.US AM');
to_timestamp
------------------------------
2008-09-21 08:15:42.95062-04
(1 row)
regression=# select to_timestamp('21-SEP-08 08.15.42.950620 PM', 'DD-MON-YY
HH.MI.SS.US AM');
ERROR: invalid AM/PM string
regression=#
Yes, those are the same command. The error is repeatable on subsequent
executions in the same session.
A likely bet is that this is caused by use of uninitialized memory,
which happens to have garbage rather than zeroes in it the second
time through.
Brendan, do you have time to look into this?
BTW, the error message is pretty unhelpful: ISTM it really ought to show
the value it's complaining of.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
