MIME-Version: 1.0
References: <CAJTYsWWNfF+hMpbsTDF8NMr+AuqoDfNxR=oHUZm7xqGP+dJ9rA@mail.gmail.com>
 <aenQ37wBgKqZb7a8@paquier.xyz> <FE1D12FF-7E5D-4ED0-A59F-BEA6DEF7EE2C@yesql.se>
 <1444609.1776958814@sss.pgh.pa.us> <d77aae98-f563-4561-b30e-699924d4d9c6@eisentraut.org>
 <ae6VJ-FllaLg92xw@paquier.xyz>
In-Reply-To: <ae6VJ-FllaLg92xw@paquier.xyz>
From: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Date: Thu, 30 Apr 2026 19:44:24 +0530
Message-ID: <CAJTYsWU0_CxphN=dfY=DCMO=n2yg4h2wvt8W=wP30zAhxoiK6A@mail.gmail.com>
Subject: Re: to_date()/to_timestamp() silently accept month=0 and day=0
To: Michael Paquier <michael@paquier.xyz>
Cc: Peter Eisentraut <peter@eisentraut.org>, Tom Lane <tgl@sss.pgh.pa.us>, 
	Daniel Gustafsson <daniel@yesql.se>, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a188ea0650ae15fb"
Archived-At: <https://www.postgresql.org/message-id/CAJTYsWU0_CxphN%3DdfY%3DDCMO%3Dn2yg4h2wvt8W%3DwP30zAhxoiK6A%40mail.gmail.com>
Precedence: bulk

--000000000000a188ea0650ae15fb
Content-Type: text/plain; charset="UTF-8"

Hi,


On Mon, 27 Apr 2026 at 04:13, Michael Paquier <michael@paquier.xyz> wrote:

> 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.
>

I'll add this to the commitfest, so that we can circle back on this
once v20 development starts.

I think parallely we can commit Daniel's v2 patch, since
that correctly documents what Postgres has right now, and we'll
know what exactly to change if we decide to go the other way.

Regards,
Ayush

--000000000000a188ea0650ae15fb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi,<div><br></div></div><br><div class=3D=
"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">O=
n Mon, 27 Apr 2026 at 04:13, Michael Paquier &lt;<a href=3D"mailto:michael@=
paquier.xyz">michael@paquier.xyz</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Fri, Apr 24, 2026 at 05:41:50PM +0200, =
Peter Eisentraut wrote:<br>
&gt; Complaints from whom?=C2=A0 Oracle rejects these, and PostgreSQL gener=
ally also<br>
&gt; rejects these dates/times in other contexts.=C2=A0 I think this should=
 be<br>
&gt; rejected.<br>
<br>
From folks who hypothetically rely on the existing zeroed inputs.=C2=A0 :)<=
br>
Perhaps it&#39;s a far-fetched argument, and just to be clear I would not<b=
r>
really object to a change of behavior on HEAD for v20, just to see<br>
where it goes in 2027.<br></blockquote><div><br></div><div>I&#39;ll add thi=
s to the commitfest, so that we can circle back on this</div><div>once v20 =
development starts.</div><div><br></div><div>I think parallely we can commi=
t Daniel&#39;s v2 patch, since</div><div>that correctly=C2=A0documents what=
 Postgres has right now, and we&#39;ll</div><div>know what exactly to chang=
e if we decide to go the other way.<br><br>Regards,<br></div><div>Ayush=C2=
=A0</div></div></div>

--000000000000a188ea0650ae15fb--