On 8/25/25, 8:30 AM, "Todd Cook" <cookt@blackduck.com <mailto:cookt@blackduck.com>> wrote:
> On 8/8/25, 6:04 PM, "Merlin Moncure" <mmoncure@gmail.com <mailto:mmoncure@gmail.com> <mailto:mmoncure@gmail.com >
<mailto:mmoncure@gmail.com>>>wrote:
>> I think it is very likely going to address your issue, but
>> confirmation helps, and will make it more likely for this patch to be
>> pushed. After that, you will have to decide to downgrade to 15 or
>> suffer the status. quo until 18 releases. Running a custom patched 17
>> is possible if a patch could be made to appear, but I do not recommend
>> it given where you are at in the release calendar.
>
> We're still working on providing confirmation. Our load testing environment depends on
> third-party PG providers, so there's a significant amount of ongoing work to set up a
> configuration where we can use a custom PG build. This is a high priority for us, so it will
> get done, though maybe not for a couple more weeks yet.
We've finished the tests comparing PG18rc1 with and without the proposed patch,
including several runs each to verify reproducibility. In short, the variance between the
two is well within what we normally see, so statistically speaking, the results are
indistinguishable. However, the results are roughly on par with what we had been
seeing with PG 15 and 16, so maybe some other change from 17 to 18 eliminated the
regression we were seeing?
-- todd
