Re: scary patch contest

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: scary patch contest
Date: 2026-08-27 18:14:37
Message-ID: CAN4CZFPBcRObk2sHJKidnuN7hJ_fG7QCdim=YnrN1sjSLFN68A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 26 Aug 2026, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I also wonder if we need some more scalable testing here, to test the
> combination of various interacting features. E.g. something like a perl script
> that generates the combinatorial combination of features around this being
> [not] used and verifies that results stay consistent. That could makes it much
> cheaper (in human time, not necessarily test runtime), to test some of the
> interactions here.

This gave me the idea to start specifically crosschecking
feature-interactions with Claude: instead of focusing on reviewing one
feature, reviewing how 2 or more features interact (for all existing
features on master, starting with an initial ranking session then
separate sessions for combinations based on that initial ranking, also
including 3-or-more feature interactions where it thinks that it would
be worth a check). The initial ranking itself surfaced 4 actual
issues, and the few more detailed runs I completed so far from the
longer task list brought up more questions/issues. The entire list
will take some time to run, I'll post some bug reports / patches.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2026-08-27 18:16:31 Re: REPACK (CONCURRENTLY) fails when table owner lacks CONNECT
Previous Message Heikki Linnakangas 2026-08-27 17:56:29 Re: pg_upgrade silently truncates nextMultiOffset to 32 bits