Re: to_date()/to_timestamp() silently accept month=0 and day=0

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: to_date()/to_timestamp() silently accept month=0 and day=0
Date: 2026-04-26 22:43:51
Message-ID: ae6VJ-FllaLg92xw@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Apr 24, 2026 at 05:41:50PM +0200, Peter Eisentraut wrote:
> Complaints from whom? Oracle rejects these, and PostgreSQL generally also
> rejects these dates/times in other contexts. I think this should be
> rejected.

From folks who hypothetically rely on the existing zeroed inputs. :)
Perhaps it's a far-fetched argument, and just to be clear I would not
really object to a change of behavior on HEAD for v20, just to see
where it goes in 2027.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-04-27 05:37:43 Re: BUG #19466: Server crash (SIGSEGV) when FETCH after ALTER TYPE during open cursor
Previous Message Andrei Lepikhov 2026-04-26 09:06:47 Re: TRAP: failed Assert("offsets[i] > offsets[i - 1]"), File: "tidstore.c"