From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, Matthias Kurz <m(dot)kurz(at)irregular(dot)at>, Himanshu Upadhyaya <upadhyaya(dot)himanshu(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Subject: | Re: SQL/JSON: JSON_TABLE |
Date: | 2022-03-25 20:30:05 |
Message-ID: | 41add101-8b91-1a3f-e002-b102402512f7@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/22/22 10:55, Daniel Gustafsson wrote:
>> On 22 Mar 2022, at 16:31, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> I'm planning on pushing the functions patch set this week and json-table
>> next week.
> My comments from 30827B3C-EDF6-4D41-BBF1-2981818744A8(at)yesql(dot)se are yet to be
> addressed (or at all responded to) in this patchset. I'll paste the ones which
> still apply to make it easier:
>
I think I have fixed all those. See attached. I haven't prepared a new
patch set for SQL/JSON functions because there's just one typo to fix,
but I won't forget it. Please let me know if there's anything else you see.
At this stage I think I have finished with the actual code, and I'm
concentrating on improving the docs a bit.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
0001-SQL-JSON-functions-without-sql_json-GUC-v59.patch | text/x-patch | 457.4 KB |
0002-JSON_TABLE-v59.patch | text/x-patch | 123.6 KB |
0003-JSON_TABLE-PLAN-DEFAULT-clause-v59.patch | text/x-patch | 27.3 KB |
0004-JSON_TABLE-PLAN-clause-v59.patch | text/x-patch | 72.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2022-03-25 20:40:37 | Re: Document atthasmissing default optimization avoids verification table scan |
Previous Message | Tom Lane | 2022-03-25 20:19:54 | Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error |