<...> > This is last commitfest for current release cycle - are you sure, so is > good idea to push all mentioned features?
Implementing standards is always a goal of the PostgreSQL community, but this is a very large patch arriving very late in the release cycle with no prior discussion.
That the patch proposed follows a standard which will not be available to the majority of reviewers is very worrisome, let alone the sheer size. While much of the code is new, I see many changes to core data structures that could very easily be destabilizing.
I propose we move this patch to the 2017-07 CF so further development and review can be done without haste and as the standard becomes more accessible.
Although I would to see these features in Postgres early I have same feeling. Is it a question if some features can be implemented easy and can be merged early?
The implementation of some JSON generation functions can be easy and the verification should not be hard. Different situation is in JSON querying functions. Merging JSONPath in first commitfest is better.
