On Thu, Sep 25, 2008 at 4:05 PM, Alex Hunsaker <[EMAIL PROTECTED]> wrote: > On Thu, Sep 25, 2008 at 10:22 AM, Tom Lane <[EMAIL PROTECTED]> wrote: >> 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. > > Yep both DCH_MC and DCH_US were going past the end of the string > because they still added the length of the string where > from_char_parse_int_len takes care of that for us now... > > The attach patch fixes it and tries to improve the "invalid AM/PM > string" a bit by showing the string.
[Actually attaches the patch...]
fix_to_timestamp.patch
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
