Re: Add pg_walinspect function with block info columns - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Add pg_walinspect function with block info columns
Date
Msg-id CAH2-WznxCuMLHad60saQubKeBp9ys=CqSV=7GetUwa+wGXMU=Q@mail.gmail.com
Whole thread Raw
In response to Re: Add pg_walinspect function with block info columns  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Wed, Mar 22, 2023 at 5:14 PM Michael Paquier <michael@paquier.xyz> wrote:
> On Wed, Mar 22, 2023 at 05:05:10PM -0700, Peter Geoghegan wrote:
> > I'd go further than that myself: I haven't had any use for FPIs at
> > all. If I was going to do something with FPIs then I'd just use
> > pg_waldump, since I'd likely want to get them onto the filesystem for
> > analysis anyway. (Just my experience.)
>
> FWIW, being able to get access to raw FPIs with a SQL interface is
> useful if you cannot log into the host, which is something that a lot
> of cloud providers don't allow, and not everybody is able to have
> access to archived WAL segments in a different host.

I'm not saying that it's not ever useful. Just that finding FPIs
interesting isn't necessarily all that common when using
pg_get_wal_block_info (or won't be, once it has those additional
columns from pg_get_wal_records_info).


--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add pg_walinspect function with block info columns
Next
From: Michael Paquier
Date:
Subject: Re: Add n_tup_newpage_upd to pg_stat table views