From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: remaining sql/json patches |
Date: | 2023-07-07 11:59:32 |
Message-ID: | CA+HiwqE6+3GFO07k1mx7z9B=rtUYcJBQFEfVvEVDUcCnY4gS1Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 7, 2023 at 8:31 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> On 21.06.23 10:25, Amit Langote wrote:
> > I realized that the patch for the "other sql/json functions" part is
> > relatively straightforward and has no dependence on the "sql/json
> > query functions" part getting done first. So I've made that one the
> > 0001 patch. The patch I posted in the last email is now 0002, though
> > it only has changes related to changing the order of the patch, so I
> > decided not to change the patch version marker (v1).
>
> (I suggest you change the version number anyway, next time. There are
> plenty of numbers available.)
Will do. :)
> The 0001 patch contains a change to
> doc/src/sgml/keywords/sql2016-02-reserved.txt, which seems
> inappropriate. The additional keywords are already listed in the 2023
> file, and they are not SQL:2016 keywords.
Ah, indeed. Will remove.
> Another thing, I noticed that the SQL/JSON patches in PG16 introduced
> some nonstandard indentation in gram.y. I would like to apply the
> attached patch to straighten this out.
Sounds fine to me.
--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey M. Borodin | 2023-07-07 12:06:19 | Re: UUID v7 |
Previous Message | Dilip Kumar | 2023-07-07 11:50:44 | Re: CHECK Constraint Deferrable |