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 1x872m-00000000v1V-0JF6 for pgsql-hackers@arkaria.postgresql.org; Sun, 20 Sep 2026 02:12:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x872k-00000005g9k-18wM for pgsql-hackers@arkaria.postgresql.org; Sun, 20 Sep 2026 02:12:38 +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.98.2) (envelope-from ) id 1x872j-00000005g9b-45Vt for pgsql-hackers@lists.postgresql.org; Sun, 20 Sep 2026 02:12:37 +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 1x872b-00000000GXX-2zO3 for pgsql-hackers@postgresql.org; Sun, 20 Sep 2026 02:12:32 +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 68K2CC84235093; Sat, 19 Sep 2026 22:12:12 -0400 From: Tom Lane To: Noah Misch cc: Heikki Linnakangas , orlovmg@gmail.com, pgsql-hackers@postgresql.org Subject: Re: 64-bit MultiXactOffset vs. 9.3->9.4 upgrade, pg_resetwal, "wraparound" msg In-reply-to: <20260919142122.52.noahmisch@microsoft.com> References: <20260827231757.78.noahmisch@microsoft.com> <8fc26d4c-ff74-4cae-9c3d-db5c4f41d4ec@iki.fi> <20260917162105.56.noahmisch@microsoft.com> <20260919142122.52.noahmisch@microsoft.com> Comments: In-reply-to Noah Misch message dated "Sat, 19 Sep 2026 07:21:22 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <235091.1789870332.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sat, 19 Sep 2026 22:12:12 -0400 Message-ID: <235092.1789870332@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Noah Misch writes: > On Fri, Sep 18, 2026 at 09:15:38PM +0300, Heikki Linnakangas wrote: >> From 866999c1251fbbde2f1d9db2799734c7c6e8fe54 Mon Sep 17 00:00:00 2001 >> From: Heikki Linnakangas >> Date: Fri, 18 Sep 2026 20:57:26 +0300 >> Subject: [PATCH 1/1] Check that oldestXID and oldestMulti are consisten= t at >> pg_upgrade > I read this patch. It looks reasonable, and I expect it provides the in= tended > defense. Thank you. The BF animals that run cross-version upgrade tests say that this fails when upgrading from 9.2 [1]: Performing Consistency Checks ----------------------------- Checking cluster versions ok Checking database connection settings ok Checking for unsupported encodings ok Checking names of databases, roles, and tablespaces ok Checking database user is the install user ok Checking for prepared transactions ok Checking oldestXID and oldestMultiXid consistency SQL command = failed SELECT datname, datfrozenxid, datminmxid FROM pg_catalog.pg_database ERROR: column "datminmxid" does not exist LINE 1: SELECT datname, datfrozenxid, datminmxid FROM pg_catalog.pg_... ^ Failure, exiting Now, we've dropped support for upgrading from 9.2 in HEAD, but we have not done so in v19, so I think this needs a fix in v19. If nothing else works, we could just skip the whole check when source server is <=3D 9.2. (I don't think this is worth breaking beta4 release freeze for, but it should get fixed afterwards.) regards, tom lane [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dcrake&dt=3D2= 026-09-19%2014%3A17%3A23