Horton

Re: Add Postgres module info

Andrei Lepikhov <lepihov@gmail.com>

View thread View on postgr.es
From: Andrei Lepikhov <lepihov@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Yurii Rashkovskii <yrashk@omnigres.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-12-16T05:02:14Z
Lists: pgsql-hackers

Attachments

On 12/13/24 10:17, Tom Lane wrote:
> Andrei Lepikhov <lepihov@gmail.com> writes:
>> On 12/12/24 21:02, Yurii Rashkovskii wrote:
>>> 2. Any reasons to dictate MAJ.MIN format? With semantic versioning
>>> abound, it's rather common to use MAJ.MIN.PATCH.
> 
>> Okay, thanks; that's a good catch. I wonder how to follow these rules
>> with a static fixed-sized structure. I would like to read about any
>> suggestions and implementation examples.
> 
> There's nothing stopping a field of the magic block from being
> a "const char *" pointer to a string literal.
Ok, See v.2 in attachment.

-- 
regards, Andrei Lepikhov

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.