Re: relfilenode statistics
Kirill Reshke <reshkekirill@gmail.com>
From: Kirill Reshke <reshkekirill@gmail.com>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
Michael Paquier <michael@paquier.xyz>, pgsql-hackers@lists.postgresql.org
Date: 2024-11-29T06:23:12Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add more tests for relation statistics with rewrites
- b23fe993e136 19 (unreleased) landed
On Tue, 5 Nov 2024 at 11:06, Bertrand Drouvot <bertranddrouvot.pg@gmail.com> wrote: > > > Does it sound ok to you to move with the above principal? (I'm +1 on it). > Hi! I looked through this thread. Looks like we are still awaiting a patch which stores more counters (n_dead_tup, ... etc) into relfilenode stats. So, I assume this should be moved to the next CF. I also have a very stupid question: If we don’t have the relation OID when writing buffers out, can we just store oid to buffertag mapping somewhere and use it? I suspect that this is a horrible idea, but what's the exact reason? Is it that we will break too many abstraction layers for such a minor matter? -- Best regards, Kirill Reshke