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 1x2BG3-005dBN-1x for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Sep 2026 17:29:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1x2BG2-001mJo-1w for pgsql-hackers@arkaria.postgresql.org; Thu, 03 Sep 2026 17:29:50 +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 1x2BG2-001mJg-0y for pgsql-hackers@lists.postgresql.org; Thu, 03 Sep 2026 17:29:50 +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 1x2BFz-00000003qN0-2suU for pgsql-hackers@lists.postgresql.org; Thu, 03 Sep 2026 17:29:49 +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 683HThCe1477912; Thu, 3 Sep 2026 13:29:43 -0400 From: Tom Lane To: Daniel Gustafsson cc: Jacob Champion , PostgreSQL Hackers , Edwin Polkerman Subject: Re: Do we want to avoid checksumming extra files in the datadir? [was: BUG #19647] In-reply-to: References: <19647-d18354ebe2134a6d@postgresql.org> Comments: In-reply-to Daniel Gustafsson message dated "Thu, 03 Sep 2026 19:20:52 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1477910.1788456583.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 03 Sep 2026 13:29:43 -0400 Message-ID: <1477911.1788456583@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Daniel Gustafsson writes: > On 3 Sep 2026, at 19:10, Jacob Champion wrote: >> The inciting event is that an extension drops a file called >> pgactive.stat into global/. We could say "don't do that", in which >> case I think we should follow Robert's idea in [1] and complain about >> the existence of the file itself rather than the lack of checksummable >> material. Or we could say "that's fine" and adjust pg_checksums to >> continue onwards if the filename isn't what we expect. > I'm not sure I have a strong preference, keeping it in sync with pg_base= backup > seems like a pretty good strategy to make it easier for users. It looks to me like there was a fair amount of consensus behind 025584a16, so I think we should conclude that pg_basebackup's new behavior (ignore stray files) is the right thing and it was an oversight that pg_checksums wasn't adjusted similarly. regards, tom lane