Re: date_part/extract parse curiosity - Mailing list pgsql-hackers

From Japin Li
Subject Re: date_part/extract parse curiosity
Date
Msg-id MEYP282MB16694BD9DFB991ED1CB64C17B62A9@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: date_part/extract parse curiosity  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 20 Oct 2022 at 22:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Japin Li <japinli@hotmail.com> writes:
>> On Thu, 20 Oct 2022 at 20:45, Erik Rijkers <er@xs4all.nl> wrote:
>>> I noticed that
>>> select date_part('millennium', now()); --> 3
>>> 
>>> will execute also, unperturbed, in this form:
>>> select date_part('millennium xxxxx', now()); --> 3
>
>> Maybe we should document this.  I'd be inclined to change the code to
>> match the certain valid field names.
>
> I think changing this behavior has a significant chance of drawing
> complaints and zero chance of making anyone happier.
>

Maybe.

> The current state of affairs (including the lack of unnecessary
> documentation detail) is likely quite intentional.
>

I'm curious about why not document this?

-- 
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: ccache, MSVC, and meson
Next
From: Robert Haas
Date:
Subject: cross-platform pg_basebackup