| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>, Bruce Momjian <bruce(at)momjian(dot)us>, amul sul <sul_amul(at)yahoo(dot)co(dot)in>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug in to_timestamp(). |
| Date: | 2016-06-23 17:29:35 |
| Message-ID: | 20160623172935.GA202223@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David G. Johnston wrote:
> On Thursday, June 23, 2016, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:
>
> > Arguing just like that one can say that we don't even need exception like
> > "division by zero". Just use well-formed numbers in denominator...
> > Input data sometimes can be generated automagically. Without exception
> > throwing debugging stored function containing to_timestamp can be painful.
>
> to_timestamp with its present behavior is, IMO, a poorly designed function
> that would never be accepted today.
I'm not sure about that.
to_timestamp was added to improve compatibility with Oracle, by commit
b866d2e2d794. I suppose the spec should follow what's documented here,
http://docs.oracle.com/cd/B19306_01/server.102/b14200/functions193.htm
http://docs.oracle.com/cd/B19306_01/server.102/b14200/sql_elements004.htm#i34924
and that wherever we deviate from that, is a bug that should be fixed.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-06-23 17:31:08 | Re: Rethinking representation of partial-aggregate steps |
| Previous Message | Robert Haas | 2016-06-23 17:26:37 | Re: Hash Indexes |