Re: Add Postgres module info
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Euler Taveira" <euler@eulerto.com>
Cc: "Andres Freund" <andres@anarazel.de>,
"Andrei Lepikhov" <lepihov@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-12-12T01:34:28Z
Lists: pgsql-hackers
"Euler Taveira" <euler@eulerto.com> writes: > +1 for the general idea. I received some reports like [1] related to wal2json > that people wants to obtain the output plugin version. Since it is not installed > via CREATE EXTENSION, it is not possible to detect what version is installed, > hence, some tools cannot have some logic to probe the module version. In a > managed environment, it is hard to figure out the exact version for > non-CREATE-EXTENSION modules, unless it is explicitly informed by the vendor. What would you foresee as the SQL API for inspecting a module that's not tied to an extension? 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