Re: Preferred way to submit a very large batch of bugs?

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Malis <malis(at)pgrust(dot)com>, pgsql-hackers(at)postgresql(dot)org, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: Preferred way to submit a very large batch of bugs?
Date: 2026-11-04 19:17:39
Message-ID: CAGRkXqTGGcrm7ibB+q4vYD7ybw+D6fSwAYBbynJqRMXBZxSWiQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Michael,

I have been sending AI-found bugs this year. Here is what worked.

Before I send one, I have Claude search the archives and the commit
log for it. There are some very good postgres mcp server such as
https://pg.ddx.io/ is good for that use case I also have skills for this
and am happy to share them.

I reproduce every bug by hand, which catches false positives. Then I
ask what kind of user/workload would hit it. A superuser-only case on a
platform you have never heard of is probably not worth sending.
A SELECT * from table that returns wrong results is a big deal.

I review every fix myself. I asked Claude to push it to a private GitHub
repo,
so I get a diff view and can ask about any line and review it.

One thing I found is that the LLM often fixes the symptom, not the root
cause.

I am sure I have made some noise too. I am happy to follow whatever
AI policy the community ends up with.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-11-04 19:49:07 Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Previous Message Manu 2026-11-04 19:09:51 Re: Progress reporting: a debug trace and a test framework