From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Xuneng Zhou <xunengzhou(at)gmail(dot)com>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer |
Date: | 2025-08-10 02:01:22 |
Message-ID: | CA+hUKGJTDW+wfcbbK=YMjBnsngQvf=TdjzLN7QmsKbpHPoaGEQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Aug 10, 2025 at 12:22 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> With all these comments and b421223172a2 already applied, are you sure
> that it is a good idea to play with the v18 branch more than
> necessary? We are in a baked beta2 state, and it looks like all these
> could qualify as HEAD-only improvements.
Yeah, b421223172a2 closes the known bug and thus the critical path item for 18.
I am happy to propose this patch as an improvement for master, and I
am not aware of remaining bugs in this area in v18. I just wanted to
publish the patch with analysis ASAP once the existing
read_stream.c/bufmgr.c interaction began to seem egregiously
suboptimal to me and I saw what to do about, having addressed the bug
with a low risk patch as a first priority. That keeps the options
open, even if not very wide given the date: on the off-chance that
others think the status quo isn't good enough and perhaps the
fragility of the existing API is actually riskier than the bigger
change, at least there's a patch on the table to discuss. I have no
plans to take any action without such a consensus.
> Perhaps the open item can be closed then?
Done.
From | Date | Subject | |
---|---|---|---|
Next Message | Maximilian Bosch | 2025-08-10 10:54:47 | Re: BUG #18991: NUMA test fails on machine with two NUMA nodes when building 18beta2 |
Previous Message | Michael Paquier | 2025-08-10 00:22:10 | Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer |