Re: scary patch contest

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scary patch contest
Date: 2026-08-25 20:15:27
Message-ID: ao3331CjzzOTxCU6@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 25, 2026 at 02:53:54PM -0400, Bruce Momjian wrote:
> On Tue, Aug 25, 2026 at 02:50:37PM -0400, Melanie Plageman wrote:
>> I don't feel like there is consensus that we need to revert this yet.
>> One thing that I'm wondering is if the ease with which LLMs allow
>> people to pressure test features means we are finding more bugs sooner
>> than we have in the past. With online checksums, as far as I
>> understand, the design has consensus and the implementation has
>> required follow-on commits but not more than other similar sized
>> features that weren't reverted. I understand that the concern is 1)
>> data corruption is especially bad and 2) if there were bugs so far,
>> who knows what more could be lurking. But I tend to wonder if 2 is
>> changing because of how easy it is to look for bugs now.
>
> If we look back at previously released features, does anyone feel these
> PG 19 features received an unusualy high number of cleanup patches? And
> if so, are there more because of AI, as Melanie is asking?

I do get the feeling that we're finding more with LLMs. Beyond that, the
RMT can use LLMs to easily find threads that ought to be added as open
items but weren't for whatever reason (e.g., the barrage of e-mails I just
sent out).

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-08-25 20:19:50 Re: RegisterShmemCallbacks() does nothing in single-user mode
Previous Message Andrey Rachitskiy 2026-08-25 20:10:12 Re: scary patch contest