Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLwB8-000WhV-2e for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Dec 2024 03:17:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tLwB5-00HTki-Jz for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Dec 2024 03:17:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLwB5-00HThC-9w for pgsql-hackers@lists.postgresql.org; Fri, 13 Dec 2024 03:17:20 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tLwB3-002Y6J-WD for pgsql-hackers@postgresql.org; Fri, 13 Dec 2024 03:17:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4BD3HFMo982749; Thu, 12 Dec 2024 22:17:15 -0500 From: Tom Lane To: Andrei Lepikhov cc: Yurii Rashkovskii , PostgreSQL-development Subject: Re: Add Postgres module info In-reply-to: <8b81a3c0-761f-4cfb-97c6-68819fe4d282@gmail.com> References: <506788.1733941263@sss.pgh.pa.us> <2c215c98-f713-4c5b-b21a-a4b8fa41890b@gmail.com> <556341.1733967371@sss.pgh.pa.us> <0844622e-9967-409a-8038-470a36f1039c@gmail.com> <8b81a3c0-761f-4cfb-97c6-68819fe4d282@gmail.com> Comments: In-reply-to Andrei Lepikhov message dated "Fri, 13 Dec 2024 09:51:58 +0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <982747.1734059835.1@sss.pgh.pa.us> Date: Thu, 12 Dec 2024 22:17:15 -0500 Message-ID: <982748.1734059835@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrei Lepikhov 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. regards, tom lane