Re: Add pg_stat_kind_info system view
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Sami Imseih <samimseih@gmail.com>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Tristan Partin <tristan@partin.io>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2026-07-01T07:07:06Z
Lists: pgsql-hackers
Attachments
- v3-0001-Add-pg_stat_kind_info-view.patch (text/plain) patch v3-0001
On Tue, Jun 30, 2026 at 11:17:29PM -0500, Sami Imseih wrote: >>> IMO, in this case, NULL should be a synonym of "I don't know", which >>> is what entry_count set to false means. 0 means "I know, there is no >>> data". I'd be OK with dropping the part about fixed-sized stats where >>> we enforce 1, and use NULL instead, though. >> >> +1, that's also my opinion [1]. > > I'm ok with that if others feel this is better. Okay, thanks. Let's do so then. Let's also invent a new pgstat_kind.c in activity/. I have been chewing a bit on the comments from Sami, leading to the following result: - Switched shared_size to entry_size, for consistency with entry_count, but I don't agree about the use of shared_data_len. shared_size is more adapted to me because it has the entry overhead and the shmem entry header. That's more precise and one does not need to guess the header size. - Moved entry_count after entry_size in the list of attributes. - written_to_file -> write_to_file, same as pgstat_internal.h. - Moved the new function to a pgstat_kind.c. - Some extra changes and tweaks to the comments, the docs, some code. The attached should do all that, hopefully. Any thoughts? -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add system view pg_stat_kind_info
- 3b066de6c0a1 master landed
-
Introduce pluggable APIs for Cumulative Statistics
- 7949d9594582 18.0 cited