Horton

Re: Bug in to_timestamp().

Artur Zakirov <a.zakirov@postgrespro.ru>

View thread View on postgr.es
From: Artur Zakirov <a.zakirov@postgrespro.ru>
To: Robert Haas <robertmhaas@gmail.com>, amul sul <sul_amul@yahoo.co.in>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "David G. Johnston" <david.g.johnston@gmail.com>, Alex Ignatov <a.ignatov@postgrespro.ru>, Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-08-25T10:11:00Z
Lists: pgsql-hackers 
>>You are right. I assigned to prev_type NODE_TYPE_SPACE to be able to
>>execute such query:
>>
>>
>>SELECT to_timestamp('---2000----JUN', 'YYYY MON');
>>
>>
>>Will be it a proper behaviour?
>
>
> Looks good to me, no one will complain if something working on PG but not on Oracle.

Thanks. I've created the entry in 
https://commitfest.postgresql.org/10/713/ . You can add yourself as a 
reviewer.

-- 
Artur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company

Commits

  1. Improve behavior of to_timestamp()/to_date() functions

  2. Implement TZH and TZM timestamp format patterns

  3. as attache of this mail is patch (to the main tree) with to_char's