Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\))
Subject: Re: to_date()/to_timestamp() silently accept month=0 and day=0
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <aenQ37wBgKqZb7a8@paquier.xyz>
Date: Thu, 23 Apr 2026 10:11:47 +0200
Cc: Ayush Tiwari <ayushtiwari.slg01@gmail.com>,
 pgsql-bugs@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE1D12FF-7E5D-4ED0-A59F-BEA6DEF7EE2C@yesql.se>
References: <CAJTYsWWNfF+hMpbsTDF8NMr+AuqoDfNxR=oHUZm7xqGP+dJ9rA@mail.gmail.com>
 <aenQ37wBgKqZb7a8@paquier.xyz>
To: Michael Paquier <michael@paquier.xyz>
Archived-At: <https://www.postgresql.org/message-id/FE1D12FF-7E5D-4ED0-A59F-BEA6DEF7EE2C%40yesql.se>
Precedence: bulk

> On 23 Apr 2026, at 09:57, Michael Paquier <michael@paquier.xyz> wrote:

> Perhaps we could consider strengthening such inputs on HEAD once v20
> opens for business?  It would be really a scary thing to backpatch,
> still a major release is a different thing.

This could definitely not be backpatched IMO, a quick check in v14 shows =
the
same behaviour.  The gregorian calendar goes from BC1 to AD1 and does =
not
define a year 0, to_date('0000','YYYY') correctly returns year 0001, =
handling
months/days in the same way at least makes it consistent (though I =
didn't scour
the archives to see if it was intentionally done like that).

--
Daniel Gustafsson