Date: Mon, 13 Jun 2016 15:52:25 +0000 (UTC)
From: amul sul <sul_amul@yahoo.co.in>
Reply-To: amul sul <sul_amul@yahoo.co.in>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Message-ID: <1873520224.1784572.1465833145330.JavaMail.yahoo@mail.yahoo.com>
Subject: Bug in to_timestamp().
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: 
 <1873520224.1784572.1465833145330.JavaMail.yahoo.ref@mail.yahoo.com>
Content-Length: 827
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Hi,

It's look like bug in to_timestamp() function when format string has more w=
hitespaces compare to input string, see below:=20

Ex.1: Two white spaces before HH24 whereas one before input time string

postgres=3D# SELECT TO_TIMESTAMP('2016-06-13 15:43:36', 'YYYY/MM/DD  HH24:M=
I:SS');
to_timestamp=20
------------------------
2016-06-13 05:43:36-07       <=E2=80=94 incorrect time=20=20=20=20=20=20=20=
=20=20=20=20=20=20
(1 row)


Ex.2: One whitespace before YYYY format string

postgres=3D# SELECT TO_TIMESTAMP('2016/06/13 15:43:36', ' YYYY/MM/DD HH24:M=
I:SS');
to_timestamp=20
------------------------------
0016-06-13 15:43:36-07:52:58      <=E2=80=94 incorrect year
(1 row)


If there are one or more consecutive whitespace in the format, we should sk=
ip those as long as we could get an actual field.
Thoughts?
Thanks & Regards,
Amul Sul


--=20
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers