Re: Incorrect "invalid AM/PM string" error from to_timestamp - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Incorrect "invalid AM/PM string" error from to_timestamp
Date
Msg-id 17771.1222443368@sss.pgh.pa.us
Whole thread Raw
In response to Re: Incorrect "invalid AM/PM string" error from to_timestamp  ("Brendan Jurd" <direvus@gmail.com>)
List pgsql-bugs
"Brendan Jurd" <direvus@gmail.com> writes:
> On Sat, Sep 27, 2008 at 12:11 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Agreed on separating the message issue.  What I wanted to know was
>> whether there are similar bugs elsewhere in to_timestamp, or whether
>> you're pretty sure this is the only occurrence of the coding pattern?

> I'm pretty sure that "MS" and "US" were the only occurrences of this
> particular coding pattern, and Alex's fix hits both of those.

OK, applied (without the message change, pending further discussion).

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Brendan Jurd"
Date:
Subject: Re: Incorrect "invalid AM/PM string" error from to_timestamp
Next
From: "Anatoli Lau"
Date:
Subject: BUG #4438: regexpression gives the error by working with [