Re: pageinspect get_raw_page() option to return invalid pages

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pageinspect get_raw_page() option to return invalid pages
Date: 2018-05-04 18:53:25
Message-ID: CAH2-WzmGb90Zs6c4T8F6xqALoN3vuEzpa6BCw8mg9jr9Fxtjog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 4, 2018 at 11:46 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Could you expand on that? Are you envisioning an option to
> ReadBufferExtended()? Because that's certainly not what I'm thinking of
> - it seems dangerous to populate shared buffers with an invalid
> page. Therefore I was more thinking to falling back to smgrread() or
> such.

I'm not envisaging anything specific just yet. It would be nice if
amcheck had an option that bypassed shared_buffers, because users want
that. That's all.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-05-04 18:56:31 Re: pageinspect get_raw_page() option to return invalid pages
Previous Message Andres Freund 2018-05-04 18:46:56 Re: pageinspect get_raw_page() option to return invalid pages