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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: to_date()/to_timestamp() silently accept month=0 and day=0
Date: 2026-04-24 12:44:04
Message-ID: 1B595919-2596-4CB3-BC39-DDCCB9876E56@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 24 Apr 2026, at 11:13, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:

> Attached patch, please review.

LGTM for the most part, I don't really think we need to use both to_date and
to_timestamp though, we can save a few cycles there. I rewrote the comments to
match the rest of the file, and moved to where to where we test for year 0000
since it seems like a better place. Also took the liberty to use year 100 in
one of the testcase, while the year is superfluous for the test in question,
year 100 was previously untested so this will increase test coverage for free.

--
Daniel Gustafsson

Attachment Content-Type Size
v2-0001-Add-regression-tests-for-zero-month-day-handling-.patch application/octet-stream 2.7 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-04-24 12:50:45 Re: to_date()/to_timestamp() silently accept month=0 and day=0
Previous Message Richard Guo 2026-04-24 12:04:03 Re: BUG #19418: SQL/JSON JSON_VALUE() does not conform to ISO/IEC 9075-2:2023(E) 6.34 <JSON value constructor>