Re: remaining sql/json patches

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remaining sql/json patches
Date: 2023-12-08 17:05:43
Message-ID: d56f74f1-5b7c-11b6-399d-2567e62b3a37@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2023-12-08 Fr 11:37, Robert Haas wrote:
> On Fri, Dec 8, 2023 at 1:59 AM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>> Would it be messy to replace the lookahead approach by whatever's
>> suiable *in the future* when it becomes necessary to do so?
> It might be. Changing grammar rules to tends to change corner-case
> behavior if nothing else. We're best off picking the approach that we
> think is correct long term.

All this makes me wonder if Alvaro's first suggested solution (adding
NESTED to the UNBOUNDED precedence level) wouldn't be better after all.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2023-12-08 17:28:09 Re: Parallel CREATE INDEX for BRIN indexes
Previous Message Robert Haas 2023-12-08 16:37:29 Re: remaining sql/json patches