Re: PG19 regression in ecd9288624a: JSON_ARRAY() indexes that go stale

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Manu <manuelreyesbravo(at)gmail(dot)com>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, shihao zhong <zhong950419(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PG19 regression in ecd9288624a: JSON_ARRAY() indexes that go stale
Date: 2026-11-05 21:41:13
Message-ID: bc6e4a60-c1bd-4fcb-9638-5f289b96a771@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2026-11-04 We 9:57 AM, Manu wrote:
>
> An option for Andrew: making every array mutable on 19, as in 18,
> also closes this, but rejects 47 more types that v5 and your patch
> accept, among them int4[] and text[], whose output no setting changed.
>
>

I think it's far too late, on the eve of RC2, to be making decisions
like this. I think the best thing we can do is revert the feature and
have another go in the next development cycle. That leaves us still with
bugs, but stops us from introducing new bugs.

I propose to do that revert tomorrow.

cheers

andrew

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-11-05 21:47:20 Re: run pgindent in CI
Previous Message Peter Eisentraut 2026-11-05 21:34:57 Re: run pgindent in CI