Re: Bug in to_timestamp().
От | amul sul |
---|---|
Тема | Re: Bug in to_timestamp(). |
Дата | |
Msg-id | 1054231194.17565594.1472116229825.JavaMail.yahoo@mail.yahoo.com обсуждение исходный текст |
Ответ на | Re: Bug in to_timestamp(). (Artur Zakirov <a.zakirov@postgrespro.ru>) |
Список | pgsql-hackers |
On Thursday, August 25, 2016 1:56 PM, Artur Zakirov <a.zakirov@postgrespro.ru> wrote: >> #2. Warning at compilation; >> >> formatting.c: In function ‘do_to_timestamp’: >> formatting.c:3049:37: warning: ‘prev_type’ may be used uninitialized in this function [-Wmaybe-uninitialized] >> if (prev_type == NODE_TYPE_SPACE || prev_type == NODE_TYPE_SEPARATOR) >> ^ >> formatting.c:2988:5: note: ‘prev_type’ was declared here >> prev_type; >> ^ >> >> You can avoid this by assigning zero (or introduce NODE_TYPE_INVAL ) to prev_type at following line: >> >> 256 + prev_type; > > >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 & Regards, Amul Sul
В списке pgsql-hackers по дате отправления: