Re: Add n_tup_newpage_upd to pg_stat table views - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Add n_tup_newpage_upd to pg_stat table views
Date
Msg-id CAH2-Wzn-rnj4U8sFwr0Tu0sGutwvuuWo8EXyCrPpUJ=LxYuthA@mail.gmail.com
Whole thread Raw
In response to Re: Add n_tup_newpage_upd to pg_stat table views  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Add n_tup_newpage_upd to pg_stat table views  (Michael Paquier <michael@paquier.xyz>)
Re: Add n_tup_newpage_upd to pg_stat table views  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
On Fri, Mar 17, 2023 at 3:22 PM Peter Geoghegan <pg@bowt.ie> wrote:
> I think that this is pretty close to being committable already.

Attached revision has some small tweaks by me. Going to commit this
revised version tomorrow morning.

Changes:

* No more dedicated struct to carry around the type of an update.

We just use two boolean arguments to the pgstats function instead. The
struct didn't seem to be adding much, and it was distracting to track
the information this way within heap_update().

* Small adjustments to the documentation.

Nearby related items were tweaked slightly to make everything fit
together a bit better. For example, the description of n_tup_hot_upd
is revised to make it obvious that n_tup_hot_upd counts row updates
that can never get counted under the new n_tup_newpage_upd counter.

--
Peter Geoghegan

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Add pg_walinspect function with block info columns
Next
From: Michael Paquier
Date:
Subject: Re: Add pg_walinspect function with block info columns