From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Melanie Plageman <melanieplageman(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add pg_walinspect function with block info columns |
Date: | 2023-03-23 00:16:09 |
Message-ID: | CAH2-WznxCuMLHad60saQubKeBp9ys=CqSV=7GetUwa+wGXMU=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 22, 2023 at 5:14 PM Michael Paquier <michael(at)paquier(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-03-23 00:24:12 | Re: Add n_tup_newpage_upd to pg_stat table views |
Previous Message | Michael Paquier | 2023-03-23 00:14:39 | Re: Add pg_walinspect function with block info columns |