| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | Re: SQL/JSON features for v15 |
| Date: | 2022-08-23 20:00:36 |
| Message-ID: | 769712.1661284836@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 2022-08-23 Tu 15:32, Jonathan S. Katz wrote:
>> On 8/23/22 1:26 PM, Andres Freund wrote:
>>> We could decide to revert this for 15, but leave it in tree for HEAD.
>> If it comes to that, I think that is a reasonable suggestion so long
>> as we're committed to making the requisite changes.
I'm not particularly on board with that. In the first place, I'm
unconvinced that very much of the current code will survive, and
I don't want people contorting the rewrite in order to salvage
committed code that would be better off junked. In the second
place, if we still don't have a shippable feature in a year, then
undoing it again is going to be just that much harder.
> One good reason for this is that way we're not fighting against the node
> changes, which complicate any reversion significantly.
Having said that, I'm prepared to believe that a lot of the node
infrastructure won't change because it's dictated by the SQL-spec
grammar. So we could leave that part alone in HEAD; at worst
it adds some dead code in backend/nodes.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-23 21:06:00 | Re: Move NON_EXEC_STATIC from c.h |
| Previous Message | Pavel Stehule | 2022-08-23 19:57:37 | Re: SQL/JSON features for v15 |