public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ashutosh Sharma <[email protected]>
To: Fujii Masao <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
Date: Tue, 9 Jun 2026 10:08:58 +0530
Message-ID: <CAE9k0PkEXWPeymZg8YmB-4_NKo3tVW3fQS-LLaWEAqstrDu9qQ@mail.gmail.com> (raw)
In-Reply-To: <CAHGQGwGBNURw4mh71_oG-fR-HCAW2-aFc05RSkmPywV97K+V3A@mail.gmail.com>
References: <[email protected]>
	<CAHGQGwGaC8RNeVP3A4_R1OcHJ-DrXgr2HH2UEYrt-Ueu516Gng@mail.gmail.com>
	<CAE9k0Pkr+KKSx4UVmrLp-ZgF1BtwoVCOHOL99MeXr81D8JnX1w@mail.gmail.com>
	<CAHGQGwGBNURw4mh71_oG-fR-HCAW2-aFc05RSkmPywV97K+V3A@mail.gmail.com>

On Fri, Jun 5, 2026 at 9:08 PM Fujii Masao <[email protected]> wrote:
>
> On Sat, Jun 6, 2026 at 12:29 AM Ashutosh Sharma <[email protected]> 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.
>

Okay, that makes perfect sense, thanks for the confirmation.

--
With Regards,
Ashutosh Sharma.

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: BUG #19508: pg_buffercache_pages() crashes the backend with an incompatible caller-supplied record definition
  In-Reply-To: <CAE9k0PkEXWPeymZg8YmB-4_NKo3tVW3fQS-LLaWEAqstrDu9qQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox