Re: Add Postgres module info
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Andrei Lepikhov <lepihov@gmail.com>,
Michael Paquier <michael@paquier.xyz>,
Euler Taveira <euler@eulerto.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-12-12T16:56:12Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2024-12-12 11:35:56 +0700, Andrei Lepikhov wrote: >> I want to say that 'cannot unload libraries' is a negative outcome of the >> architecture. It would be better to invent something like PG_unregister, >> allowing libraries to at least return a hook routine call back to the >> system. > I am quite certain we'll not support unloading libraries anytime soon. We used > to support it and it caused problems... Changing anything about how exactly > things are tracked in dfmgr.c will be the smallest part of supporting > unloading libraries again. Indeed. However, I don't see what that has to do with the current discussion anyway. The proposed SRF would iterate through whatever is in the DynamicFileList. What does it care whether there's a way to add or remove entries? 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