Re: scary patch contest

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, bruce(at)momjian(dot)us
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scary patch contest
Date: 2026-08-25 20:10:12
Message-ID: CAB8bMit5vwAYHJtq5SqkXKLZaJjBNKDgRdOyDPMqy6+Y2KnorQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ср, 26 авг. 2026 г. в 00:29, Andrew Dunstan <andrew(at)dunslane(dot)net>:

> I do think we need to be smarter about using LLMs
> methodically to detect and test for bugs more comprehensively, not as an
> alternative to human efforts but as a useful supplement.
>
>
As someone who does fuzzing, finds bugs in the code, and spends free time
going through bug mailing lists and trying to fix issues - let me share my
perspective.

Melanie made a good point - LLMs are making it easier for people to find
bugs, and that's definitely true. But at the same time, they also help us
respond to those findings more quickly.

That said, only those who do nothing are mistake-free.

Maybe we should be writing more tests and thinking more broadly during the
design phase. That alone won't solve everything, but it could help catch
things earlier.

From where I stand, fixing a bug is only half the battle. We need the
change to be merged into master. Reviews are generally easy to come by -
there's almost always someone who can do them. However, making sure that a
committer or the subsystem maintainer notices something in the bug mailing
list requires effort and a bit of ingenuity.

--
Regards,
Rachitskiy Andrey

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-08-25 20:15:27 Re: scary patch contest
Previous Message Nathan Bossart 2026-08-25 20:00:59 Re: RegisterShmemCallbacks() does nothing in single-user mode