Request a Demo
Home   >   mailing lists

Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition - Mailing list pgsql-bugs

From Fujii Masao
Subject Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
Date
Msg-id CAHGQGwGBNURw4mh71_oG-fR-HCAW2-aFc05RSkmPywV97K+V3A@mail.gmail.com
Whole thread
Responses Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
List pgsql-bugs
Tree view 
On Sat, Jun 6, 2026 at 12:29 AM Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
> pg_buffercache_pages uses RETURNS SETOF RECORD whereas other
> extensions like pgstattuple define explicit IN/OUT parameters at the
> SQL level. Is there a specific reason this pattern was kept, or is it
> simply a legacy design that hasn't been modernized? Had we followed
> the IN/OUT parameter style, this sort of issue could have been
> avoided, no?

Probably yes. But if we do that, we would likely need to bump pg_buffercache
version. I'm not sure that's worthwhile just for this change.

Regards,

--
Fujii Masao

pgsql-bugs by date:

Previous
From: Fujii Masao
Date:
Subject: Re: BUG #19511: contrib/dblink: NULL dereference in dblink_get_notify() when called without a prior connection
Next
From: "Matheus Alcantara"
Date:
Subject: Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct