On Dec 11, 2024, at 19:49, Euler Taveira <eu...@eulerto.com> wrote: >> FWIW, Id like to have some more information in there, without commenting on >> the specifics. > > +1 for the general idea.
Same. > 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. I’m all for additional metadata for native extensions, but I’d also like to draw attention to the “Future” section my proposal[1] to require that module-only extensions also include a control file and be loadable via CREATE EXTENSION (and proposed *_preload_extensions GUCs[2]). This would unify how all types of extensions are added to a database, and would include version information as for all other CREATE EXTENSION extensions. Not a mutually-exclusive proposal, of course; I think it makes sense to have metadata included in the binary itself. Would be useful to compare against what CREATE EXTENSION thinks is the version and raising an error or warning when they diverge. Best, David [1]: https://justatheory.com/2024/11/rfc-extension-packaging-lookup/#future-deprecate-load [2]: https://justatheory.com/2024/11/rfc-extension-packaging-lookup/#extension-preloading
