| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
| Cc: | "Alex Hunsaker" <badalex(at)gmail(dot)com>, "Joshua Tolley" <eggyknap(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Incorrect "invalid AM/PM string" error from to_timestamp |
| Date: | 2008-09-26 15:36:08 |
| Message-ID: | 17771.1222443368@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> On Sat, Sep 27, 2008 at 12:11 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anatoli Lau | 2008-09-27 00:46:31 | BUG #4438: regexpression gives the error by working with [ |
| Previous Message | Brendan Jurd | 2008-09-26 14:35:26 | Re: Incorrect "invalid AM/PM string" error from to_timestamp |