Re: [HACKERS] SQL/JSON in PostgreSQL - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] SQL/JSON in PostgreSQL
Date
Msg-id CAFj8pRBzv04uv+-dN-2E0tOxurupmkDfD=quj=aatvpJ=c9Jhg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] SQL/JSON in PostgreSQL  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] SQL/JSON in PostgreSQL
List pgsql-hackers


2017-09-29 12:15 GMT+02:00 Pavel Stehule <pavel.stehule@gmail.com>:


2017-09-29 12:09 GMT+02:00 Nikita Glukhov <n.gluhov@postgrespro.ru>:


I have some free time now. Is it last version?

Regards

Pavel

Yes, this is still the latest version. Now I am working only on unfinished WIP
patch no. 9, but I think it should be reviewed the last.



ok

Thank you

I have few queries and notes

1. Why first patch holds Gin related functionality? Can be it separated?

2. Why Json path functions starts by "_" ? These functions are not removed by other patches.

3. What is base for jsonpath-extensions? ANSI/SQL?

This patch is pretty big - so I propose to push JSONPath and SQL/JSON related patches first, and then in next iteration to push JSON_TABLE patch. Is it acceptable strategy? I am sure so JSON_TABLE is pretty important function, but it is pretty complex too (significantly more complex than XMLTABLE), so it can be practiacal to move this function to separate project. I hope so all patches will be merged in release 11 time.

Regards

Pavel



Pavel

--
Nikita Glukhov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: [HACKERS] alter server for foreign table
Next
From: chenhj
Date:
Subject: Re: [HACKERS] [PATCH]make pg_rewind to not copy useless WALfiles