| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org, maralist86(at)mail(dot)ru |
| Subject: | Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL |
| Date: | 2025-06-08 15:40:11 |
| Message-ID: | 182094.1749397211@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> writes:
> Out of curiosity, why aren't we applying this to v18?
Our risk-aversion level rises steadily over the course of a release
cycle, and is pretty high post beta1. While I think the problems
we're trying to fix here are real, they are very low-probability
(I don't recall hearing any field reports traceable to this).
And you have to remember there is also some risk of introducing
new bugs. On balance it's not a change I would back-patch, and
at this point v18 is pretty close to being a stable branch so
it's not getting fixes we wouldn't back-patch, unless that's
because they are in new-in-18 code.
tl;dr: I agree with Michael's choice to hold it for v19.
It's a judgment call of course, but I think it's the right one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2025-06-08 15:44:02 | Re: BUG #18951: Precision loss in inner join while using SUM aggregate function |
| Previous Message | PG Bug reporting form | 2025-06-08 14:38:55 | BUG #18951: Precision loss in inner join while using SUM aggregate function |