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.98.2) (envelope-from ) id 1xTVLz-00000000Mrk-1Emx for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Nov 2026 02:24:55 +0000 Received: from localhost ([127.0.0.1]:42960 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xTVLy-00000008Jkz-2pwn for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Nov 2026 02:24:54 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:57834) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xTVLy-00000008Jkl-1Tzb for pgsql-hackers@lists.postgresql.org; Wed, 18 Nov 2026 02:24:54 +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.98.2) (envelope-from ) id 1xTVLw-00000000EyJ-0ehQ for pgsql-hackers@postgresql.org; Wed, 18 Nov 2026 02:24:53 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 6AI2Oonv603097; Tue, 17 Nov 2026 21:24:50 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 sss.pgh.pa.us 6AI2Oonv603097 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sss.pgh.pa.us; s=default; t=1794968690; bh=Nz332kGugX1cfn5F439E40aDP1NTxlVIgb3ycSkqY7w=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=nj6MhE7leUjTmfLjUYbkMER/FDg9X6i4hPhyu/IaQ2huvLHSCOfVnxLrWJ0Us6Ba2 r3B7Qq35afPZ/pFQmg7JroaCyEWAgbVIcp1SyC8AcCMVbEFH4qjKxb9jDE2/nZamIt GmpT4PadE6lafqg1XOrJFWyWavieVIo3ZC6AGnxE= From: Tom Lane To: Andrew Dunstan cc: Nathan Bossart , pgsql-hackers@postgresql.org Subject: Re: create .abi-compliance-history file for v19 In-reply-to: <123E4F2E-4465-4607-9FA8-735E647E9522@dunslane.net> References: <123E4F2E-4465-4607-9FA8-735E647E9522@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Tue, 17 Nov 2026 21:22:07 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <603095.1794968690.1@sss.pgh.pa.us> Date: Tue, 17 Nov 2026 21:24:50 -0500 Message-ID: <603096.1794968690@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > Should this be added to release procedures? It's mentioned in RELEASE_CHANGES, although perhaps not very prominently. We don't have a separate section there for post-major-release steps. regards, tom lane