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 1twk8A-00HBui-Cw for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Mar 2025 15:54:26 +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 1twk89-005VIO-28 for pgsql-hackers@arkaria.postgresql.org; Mon, 24 Mar 2025 15:54:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1twk88-005VI9-P4 for pgsql-hackers@lists.postgresql.org; Mon, 24 Mar 2025 15:54:24 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1twk86-000ttk-1r for pgsql-hackers@postgresql.org; Mon, 24 Mar 2025 15:54:24 +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 52OFsHDT1003654; Mon, 24 Mar 2025 11:54:17 -0400 From: Tom Lane To: Robert Haas cc: Andrei Lepikhov , Michael Paquier , Alexander Korotkov , Yurii Rashkovskii , PostgreSQL-development Subject: Re: Add Postgres module info In-reply-to: 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> <982748.1734059835@sss.pgh.pa.us> <0e82bf8c-ae70-498d-861e-dba2bb154cad@gmail.com> <29d29c3e-ac9e-48cc-87b4-b1cfd8c2ede8@gmail.com> <992ec366-5c0d-4f23-a02e-30e663613f44@gmail.com> <4476e8cd-6427-4470-98a8-8d61b82d8b1e@gmail.com> <441661.1742683797@sss.pgh.pa.us> <796058.1742757002@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 24 Mar 2025 10:31:27 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1003652.1742831657.1@sss.pgh.pa.us> Date: Mon, 24 Mar 2025 11:54:17 -0400 Message-ID: <1003653.1742831657@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > It looks reasonable to me. I am a bit worried that using PG_VERSION as > the version string is going to feel like the wrong thing at some > stage, but I can't really say why, and I think it's better to do > something now and maybe have to revise it later than to do nothing now > and hope that we come up with a brilliant idea at some point in the > future. Agreed. I think something is clearly better than nothing here, and PG_VERSION has the huge advantage that we need no new mechanism to maintain it. (A version identifier that isn't updated when it needs to be is worse than no identifier, IMO.) If somebody thinks of a better idea and is willing to do the legwork to make it happen, we can surely change to something else later on. Or invent another field with different semantics, or whatever. regards, tom lane