| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | 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 18:53:54 |
| Message-ID: | ao3kwgxtr49LnbAi@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2026-08-25 18:54:21 | Re: scary patch contest |
| Previous Message | Melanie Plageman | 2026-08-25 18:50:37 | Re: scary patch contest |