Re: Bug in to_timestamp().

From: Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in to_timestamp().
Date: 2016-08-25 10:11:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
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 . You can add yourself as a

Artur Zakirov
Postgres Professional:
Russian Postgres Company

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message amul sul 2016-08-25 10:26:39 Re: Bug in to_timestamp().
Previous Message Tatsuki Kadomoto 2016-08-25 09:45:30 Checksum error and VACUUM FULL