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.96) (envelope-from ) id 1x10Lf-004vhH-1L for pgsql-hackers@arkaria.postgresql.org; Mon, 31 Aug 2026 11:38:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x10Le-00HVol-1E for pgsql-hackers@arkaria.postgresql.org; Mon, 31 Aug 2026 11:38:46 +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.96) (envelope-from ) id 1x10Le-00HVod-0L for pgsql-hackers@lists.postgresql.org; Mon, 31 Aug 2026 11:38:46 +0000 Received: from mail-wm1-x330.google.com ([2a00:1450:4864:20::330]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1x10Lc-00000003IFP-0DQl for pgsql-hackers@lists.postgresql.org; Mon, 31 Aug 2026 11:38:44 +0000 Received: by mail-wm1-x330.google.com with SMTP id 5b1f17b1804b1-49b0d8bc2aaso33438565e9.0 for ; Mon, 31 Aug 2026 04:38:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1788176322; x=1788781122; darn=lists.postgresql.org; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:from:to:cc:subject :date:message-id:reply-to:content-type; bh=RvBNpXNMSI2m7FGLrFjg7iyBOUH2+mWs1Fuwog4Ddxc=; b=sIvyF5W3bExiIEtcremhg/HEkhgYi0Qsfhi2cNxWnurZ4V/wsc0acL5OY0eDYyicl1 gkgE3Mucr1ZJWi1Iv/FmbtSaqvbh3TBj226gZdHVV1qTxMPAbydNF7rmeaxr2AuNs7aa vxi3uQBqjlq8wFKEpJRTKh02wXBKqXQoaOktjd7c1VcLvb+VPk8oyIuswiy+4ZC3YHn7 7JIRSTCJbaCbEcFrp8ivtnK21oBQfVo3Pg7eN+loovubh2rNWAncuPrHnFfnFR7HfTx8 L7q5wP5OUXq6Usnt1x7YzfRIoBsAewuTY+mzNkf3nADv4LRzar33VIXOzxn3t0dV1DFu tGDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788176322; x=1788781122; h=in-reply-to:content-disposition:content-type:mime-version :references:message-id:subject:cc:to:from:date:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=RvBNpXNMSI2m7FGLrFjg7iyBOUH2+mWs1Fuwog4Ddxc=; b=Q5cqMO/J3Q2/xHE4UBVd30GsKulKbiXhnxO7lrI0JodcdOKmIRc0vC9VvOPu0J2mOT Gbs+FYG0UF+ZfLNhfRw551d52W1MKrKd6x7aZQ38aq+d5yGqwtbFqfaJGYjwdwodn0Wm 7AUuouxQmml4mFo6LG4F6MyRNeSEVHUQ4Un18MPY45plq9H9J8tNMjDgYvrCBaLQLQCB MGlyKjFwZF5o8pLBfT+DftSHO6ZMkIOqVPwGLJAt1qS4LsxKNEeo/l9571OCig/3whFv ItteQFBR2dTHr9wis+hirUVaagiUtE4ZkbFaawiygw9Wxg7XMVqLN4dQPzKIpS8uE8mM D0aA== X-Forwarded-Encrypted: i=1; AHgh+RqiV/IP50LQ2z1rFNRpuli5YDbxoDxJKsLUb6n7Qs1/80/BeWUbkRxSUS+EZ2J2HudiyijDm3daKgIRChGW@lists.postgresql.org X-Gm-Message-State: AFuF++kC7k9ZFnNiSRNb4D3ZNtf+wxb+c5drp+qmt12abFTa96Wmeg9u MXRCKTwAu6vECzeZTi7kpN2hQlMxq1JEmjtf37hgwDWXAyIpx7tGq8Ud X-Gm-Gg: AR+sD12woBbyS2wLY5zcYem7/nsHMseGI40YsyqDLk+UF5W5nAPfJH2/vev79lfsYS1 6pfPWcPzzNfIVIkGIthSm6rOjDseho6MCUBM/HmX4DGItrSZp0n71oFTidtgiClrSrXf5TPI3ko nDu8sW2cGpFtJJ4w5cj+HtfoqUNtwcnaru+93wLNwAhFNYPpQs5wD4tjNbk0Z+gRkbEMwFb1fIu F7PVrsW2cjCFSaFEpsdKvAnroPFAvQqT4txBVHd6385EdsR++fkwp461sSNNjyyNMRcVOmDl1o3 vwIPzv6P4ZsrOxI11V4367sq8WV+QdhUxFULrx6Ku1EGHZL0NmWI9Rk5RQ70VX1pMKbuIMj5H9y UQ4vIPOgPAG2uORTkrNuGnjb4cE8QMAVTXUYHNaGCGFSnZKwkKlS/od6GkHRmvgnIaP6iVP5sIN mm4mKPFURWHFHgJzDYvUMchPOLHp/wF81YHKtTWDjaOp/6fzyt+qkFkp+hCMXosWaBYGOzAgAJU oVjWmqDuKIv0+eVGCTD7z+2RpcMvzzjQYEvq+WOsLIiUv82 X-Received: by 2002:a05:600c:1d1d:b0:49b:d45:703e with SMTP id 5b1f17b1804b1-49b91c2dfecmr382678345e9.8.1788176322199; Mon, 31 Aug 2026 04:38:42 -0700 (PDT) Received: from bdtpg (ec2-15-237-197-144.eu-west-3.compute.amazonaws.com. [15.237.197.144]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-49cca3e642dsm167767115e9.2.2026.08.31.04.38.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Aug 2026 04:38:41 -0700 (PDT) Date: Mon, 31 Aug 2026 11:38:40 +0000 From: Bertrand Drouvot To: Zsolt Parragi Cc: Daniel Gustafsson , pgsql-hackers@lists.postgresql.org Subject: Re: Offline data checksum changes can cause incorrect checksum state on standbys Message-ID: References: <8DCA12FF-0199-403D-A203-666528A25DB6@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Mon, Aug 31, 2026 at 11:55:01AM +0100, Zsolt Parragi wrote: > > Yeah, I see your point that the underlying issue is the non WAL logged change. > > My concern was not about a pg_control change in itself, but that addressing this > > case might require further changes to the current pg_control design, which adds > > risk this close to RC1. > > I don't think we can get this completely right without both wal and > pg_control changes (and possibly some extra connection-time > communication between the standby and primary to provide early > reporting instead of delayed in the most common cases) > If we want to move toward the error direction in pg20 (which we > should) we will have to log that an offline change happened. > > I attached v6 which for now documents the current behavior as-is, and > other than that I reorganized the test files. Thanks! I did not look in details but it looks like that pg_upgrade --check against a running source cluster with checksums enabled will still fail (finding === 2 in [0], tested with the test shared in [1]). [0]: https://postgr.es/m/apUL3N4IE934qJ08%40bdtpg [1]: https://postgr.es/m/apU4/hmRv/4gv20W%40bdtpg Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com