MIME-Version: 1.0
References: <CAJTYsWWNfF+hMpbsTDF8NMr+AuqoDfNxR=oHUZm7xqGP+dJ9rA@mail.gmail.com>
 <aenQ37wBgKqZb7a8@paquier.xyz> <FE1D12FF-7E5D-4ED0-A59F-BEA6DEF7EE2C@yesql.se>
In-Reply-To: <FE1D12FF-7E5D-4ED0-A59F-BEA6DEF7EE2C@yesql.se>
From: Ayush Tiwari <ayushtiwari.slg01@gmail.com>
Date: Thu, 23 Apr 2026 13:56:01 +0530
Message-ID: <CAJTYsWVf7wPE9YWL5Bf310KzWPJiQ9JiW8rT_wtjSiLtAzBCGg@mail.gmail.com>
Subject: Re: to_date()/to_timestamp() silently accept month=0 and day=0
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b5962206501c6602"
Archived-At: <https://www.postgresql.org/message-id/CAJTYsWVf7wPE9YWL5Bf310KzWPJiQ9JiW8rT_wtjSiLtAzBCGg%40mail.gmail.com>
Precedence: bulk

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

Hi,

On Thu, 23 Apr 2026 at 13:41, Daniel Gustafsson <daniel@yesql.se> wrote:

> > 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).
>
>
++ on not backporting it since it may break existing applications.

 But we should consider strengthening such inputs for v20.

Regards,
Ayush

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

<div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail_quote gmail_quote_co=
ntainer"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 23 Apr 2026 at 13:41=
, Daniel Gustafsson &lt;<a href=3D"mailto:daniel@yesql.se">daniel@yesql.se<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&=
gt; On 23 Apr 2026, at 09:57, Michael Paquier &lt;<a href=3D"mailto:michael=
@paquier.xyz" target=3D"_blank">michael@paquier.xyz</a>&gt; wrote:<br>
<br>
&gt; Perhaps we could consider strengthening such inputs on HEAD once v20<b=
r>
&gt; opens for business?=C2=A0 It would be really a scary thing to backpatc=
h,<br>
&gt; still a major release is a different thing.<br>
<br>
This could definitely not be backpatched IMO, a quick check in v14 shows th=
e<br>
same behaviour.=C2=A0 The gregorian calendar goes from BC1 to AD1 and does =
not<br>
define a year 0, to_date(&#39;0000&#39;,&#39;YYYY&#39;) correctly returns y=
ear 0001, handling<br>
months/days in the same way at least makes it consistent (though I didn&#39=
;t scour<br>
the archives to see if it was intentionally done like that).<br><br></block=
quote><div><br>++ on not backporting it since it may break existing applica=
tions.<br><br>=C2=A0But we should consider strengthening such inputs for v2=
0.<br><br>Regards,<br>Ayush</div></div></div>

--000000000000b5962206501c6602--