Re: Add Postgres module info
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Euler Taveira <euler@eulerto.com>, Andres Freund <andres@anarazel.de>,
Andrei Lepikhov <lepihov@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-12-12T03:39:38Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > On Wed, Dec 11, 2024 at 08:34:28PM -0500, Tom Lane wrote: >> What would you foresee as the SQL API for inspecting a module that's >> not tied to an extension? > Rather than a function that can be called with a specific module name > in input, invent a new system SRF function that would report back for > a process all the libraries that have been loaded in it? Yeah, that could work. > Presumably, > the extra tracking can be done in dfmgr.c with more fields added to > DynamicFileList to track the information involved. I wouldn't add any overhead to the normal case for this. Couldn't we walk the list and re-fetch each module's magic block inside this new function? regards, tom lane
Commits
-
Avoid mixing designated and non-designated field initializers.
- d66997dfe8fe 18.0 landed
-
Use PG_MODULE_MAGIC_EXT in our installable shared libraries.
- 55527368bd07 18.0 landed
-
Introduce PG_MODULE_MAGIC_EXT macro.
- 9324c8c58065 18.0 landed