From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: timestamptz parsing bug? |
Date: | 2011-08-29 19:30:02 |
Message-ID: | 10516.1314646202@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
> On 29 August 2011 15:40, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> Why do we parse this as a correct timestamptz literal:
>> 2011-08-29T09:11:14.123 CDT
>> but not this:
>> 2011-08-29T09:11:14.123 America/Chicago
> For this input string the "T" is recognised as the start of an ISO
> time, and the ptype variable is set to DTK_TIME. The next field is a
> DTK_TIME, however, when it is handled it doesn't reset the ptype
> variable.
> When it gets to the timezone "America/Chicago" at the end, this is
> handled in the DTK_DATE case, because of the "/". But because ptype is
> still set, it is expecting this to be an ISO time, so it errors out.
Do we actually *want* to support this? The "T" is supposed to mean that
the string is strictly ISO-conformant, no?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2011-08-29 19:35:25 | Re: timestamptz parsing bug? |
Previous Message | Greg Smith | 2011-08-29 19:24:17 | Re: Displaying accumulated autovacuum cost |