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 16029.1222438279@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>)
Responses Re: Incorrect "invalid AM/PM string" error from to_timestamp
Re: Incorrect "invalid AM/PM string" error from to_timestamp
List pgsql-bugs
"Brendan Jurd" <direvus@gmail.com> writes:
> I have some thoughts on this and other issues surrounding AM/PM, but
> perhaps they are better reserved for a separate thread.  Might I
> suggest we apply Alex's bugfix and hold off on the message changes
> pending further discussion?

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've always found it helpful to think "where else did we make this
same mistake" after identifying a bug.

            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: "Joshua Tolley"
Date:
Subject: Re: Incorrect "invalid AM/PM string" error from to_timestamp