Re: Prevent crash when calling pgstat functions with unregistered stats kind
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Ewan Young <kdbase.hack@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-07-02T05:00:06Z
Lists: pgsql-hackers
On Thu, Jul 02, 2026 at 04:43:32AM +0000, Bertrand Drouvot wrote: > On Thu, Jul 02, 2026 at 04:23:16AM +0000, Bertrand Drouvot wrote: >> Ok but what about extensions that don't call pgstat_register_kind() at all? Your >> point is that they would see the issue during the development of the extension? (If >> so, I think I could agree). Extensions doing custom stats have to call the register API, or they're broken. This is the same assumption as custom RMGRs. There are many ways to break the backend if you don't know what you do, just take hooks for example. That's just one of them. > Something like in the attached? Yes, that looks OK here. -- Michael
Commits
-
test_custom_stats: Fail if loading module outside shared_preload_libraries
- 7838efe9a2d1 19 (unreleased) landed
- 5045d9ff3b5a master landed