| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scary patch contest |
| Date: | 2026-08-25 22:33:04 |
| Message-ID: | 646368.1787697184@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I asked Claude to evaluate which v19 patches were the scariest based
> on the number and type of bugs fixed post-freeze. Results below, with
> a few particularly cutting remarks from the LLM edited out.
...
> 5. SQL/PGQ property graphs (2f094e7ac69, Peter Eisentraut and Ashutosh
> Bapat): 17 fixes, but lower severity — wrong collation, unresolved
> literals, broken LATERAL references, deparse and pg_dump ACL bugs,
> plus a series of after-the-fact prohibitions.
...
FWIW, I am quite afraid of #5, mainly because we are *still*
discussing fixes that will require parsetree and/or catalog changes
and thus catversion bumps. (There are two such threads on the
open-items list, and possibly more that I've not noticed.) At this
point I'd be willing to bet dinner that if we ship it in v19 there
will be post-release bug discoveries that are unfixable until v20.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-08-25 22:38:35 | Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row |
| Previous Message | Bharath Rupireddy | 2026-08-25 22:24:00 | Re: Assertion failure in GetSubscriptionRelations() with concurrent DROP TABLE |