Horton

Re: Add Postgres module info

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@justatheory.com>
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-23T20:17:47Z
Lists: pgsql-hackers 
"David E. Wheeler" <david@justatheory.com> writes:
> 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.

How would that work for extensions where the C code is intentionally
supporting multiple versions of the SQL objects?

			regards, tom lane

Commits

  1. Avoid mixing designated and non-designated field initializers.

  2. Use PG_MODULE_MAGIC_EXT in our installable shared libraries.

  3. Introduce PG_MODULE_MAGIC_EXT macro.