From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add Postgres module info |
Date: | 2024-12-12 01:36:11 |
Message-ID: | 556341.1733967371@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrei Lepikhov <lepihov(at)gmail(dot)com> writes:
> It makes sense. But I want to clarify that I avoided changing
> PG_MODULE_MAGIC because the newly introduced structure has a totally
> different purpose and usage logic: the struct is designed to check
> compatibility, but module info isn't connected to the core version at
> all: a single version of the code may be built for multiple PG versions.
> At the same time, various versions of the same library may be usable
> with the same core.
Surely. But I don't see a need for two separately-looked-up
physical structures. Seems to me it's sufficient to put the
ABI-checking fields into a sub-struct within the magic block.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-12-12 01:41:16 | Re: pg_createsubscriber TAP test wrapping makes command options hard to read. |
Previous Message | Tom Lane | 2024-12-12 01:34:28 | Re: Add Postgres module info |