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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "manuelreyesbravo(at)gmail(dot)com" <manuelreyesbravo(at)gmail(dot)com>, andrew(at)dunslane(dot)net, jian(dot)universality(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, zhong950419(at)gmail(dot)com
Subject: Re: PG19 regression in ecd9288624a: JSON_ARRAY() indexes that go stale
Date: 2026-11-04 18:04:28
Message-ID: rxpqwrfkugupf7v4xua54gzua7go2pkcq7bxllksayrfbjttnm@u6witg5aqlp6
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-11-03 22:37:52 -0800, Nikolay Samokhvalov wrote:
> AI found this while testing v5 and prepared the attached patch; I
> haven't manually reviewed the code yet.

Personally I think dropping unverified AI code onto the list has almost always
negative value, it just increases the already really high noise floor even
further. We all can ask LLMs to vomit out code. Putting it on the list
basically just means you're asking somebody else to do the actual work.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-11-04 18:08:07 Re: nbtree: opt-in leaf key prefix compression
Previous Message Andres Freund 2026-11-04 17:59:55 Re: Preferred way to submit a very large batch of bugs?