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-29T15:52:13Z
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 Fri, 29 Nov 2024 at 20:20, Bertrand Drouvot <bertranddrouvot.pg@gmail.com> wrote: > On Fri, Nov 29, 2024 at 11:23:12AM +0500, Kirill Reshke wrote: > > If we don’t have the relation OID when writing buffers out, can we > > just store oid to buffertag mapping somewhere and use it? > > Do you mean add the relation OID into the BufferTag? While that could probably > be done from a technical point of view (with probably non negligible amount > of refactoring), I can see those cons: Not exactly, what i had in mind was a separate hashmap into shared memory, mapping buffertag<>oid. > 2. Probably lot of refactoring > 3. This new member would be there "only" for stats and reporting purpose as > it is not needed at all for buffer related operations To this design, your points 2&3 apply. -- Best regards, Kirill Reshke