<...> > 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.
We discussed this in Brussels, but I agree, the patch is rather big.
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 don't know when the standard will be publicly available.
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.
I wanted to have one more good feature in 10 and let postgres be on par with other competitors. SQL/JSON adds many interesting features and users will be dissapointed if we postpone it for next two years. Let's wait for reviewers, probably they will find the patch is not very intrusive. We have a plenty of time and we dedicate one full-time developer for this project.
