Re: remaining sql/json patches - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: remaining sql/json patches
Date
Msg-id 4672bd9a-e9db-a71d-6b74-f7c68f8b89cd@eisentraut.org
Whole thread Raw
In response to Re: remaining sql/json patches  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: remaining sql/json patches
List pgsql-hackers
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.)

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.

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

pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Add hint message for check_log_destination()
Next
From: Dilip Kumar
Date:
Subject: Re: CHECK Constraint Deferrable