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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Cc: n(dot)kalinin(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
Date: 2026-06-05 15:38:15
Message-ID: CAHGQGwGBNURw4mh71_oG-fR-HCAW2-aFc05RSkmPywV97K+V3A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Jun 6, 2026 at 12:29 AM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Ashutosh Sharma 2026-06-05 15:29:23 Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition