On Thu, Sep 24, 2026 at 2:26 PM Ma Xueting <[email protected]> wrote: > The analogous local-buffer error, "no empty local buffer available", > is already reported using ERRCODE_INSUFFICIENT_RESOURCES.
Isn't it better to add "shared" to the error message to clarify which buffers are involved, as the local-buffer message does? For example, "no unpinned shared buffers available" or "could not find an unpinned shared buffer". BTW, I prefer the latter because "could not" describes the failed attempt more clearly. If we adopt this, for consistency, it might be better to also change the local-buffer message to something like "could not find an unpinned local buffer". Regards, -- Fujii Masao
