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

From: Kirk Wolak <wolakk(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, 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, Robert Haas <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 21:07:39
Message-ID: CACLU5mQCmgSVn84F+HrXDakdyLs2_nRhyeBt9HKn84u4Az9QCw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 4, 2026 at 1:45 PM Andres Freund <andres(at)anarazel(dot)de> wrote:

>
> The lists are clearly getting less and less readable. Parts of that is an
> increase in the rate of issues being found - those are ofen real, and we
> have
> to somehow deal with that. Part of that is lots of entities doing
> automated
> patch review via the list. That's not useful and makes seeing actual
> content
> ever harder.
>
> I don'd see how making the lists unreadable is in the interest of even the
> biggest LLM fan. Having lots of patches that no human looks at ever doesn't
> help anyone. So I think we need to start enforcing some basic rules around
> what is and what isn't ok.
>
>
To be clear, we can agree here. Step 1 on a conversation with Nik and
Andrey was the concept of
human conversation plus [x] footnotes that reference the AI stuff you do
not want to see (and we want to be clear).

Footnoting seems like the PG approach here that should work. (Making the
research part of what
other AIs might want to consume, still available).

Also, in defense of Nik, he is not using "some LLM in chat". He is on
the cutting edge with tooling.
He has created (and tested, and improved) a group of working AIs that have
found numerous bugs,
then used other models to confirm they are real. He has gone as far as
integrating them into performance
monitoring down to OS Flame Graphs... Using various levels of AI
interaction. Rerunning things for days
until he, as an intelligent human, is concurring there is an issue... (ie,
this is NOT AI slop)

So, this problem is going to keep coming up. I personally AGREE with you
that we want to separate
what the AI was doing from the HUMAN discussion that requires
comprehension, in order to reduce the
cognitive load on the humans. How?

This is step one. But your response seemed to imply that AI related
patches and fixes are all the same,
and you don't want to see any part of them. Clarify if I am not correct.

My question is simply... Should we set a rule that such LLM generated
stuff should always be a footnote?
Personally, I think this makes sense. What say you?

Thanks!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-11-04 21:09:44 Re: Use WALReadFromBuffers in more places
Previous Message Jelte Fennema-Nio 2026-11-04 21:07:14 Re: Python/pytest test framework take two