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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1voSU3-0051Ia-2U
	for pgsql-hackers@arkaria.postgresql.org;
	Fri, 06 Feb 2026 20:31:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1voSU2-005QEn-2v
	for pgsql-hackers@arkaria.postgresql.org;
	Fri, 06 Feb 2026 20:31:18 +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.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1voSU2-005QEf-1y
	for pgsql-hackers@lists.postgresql.org;
	Fri, 06 Feb 2026 20:31:18 +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.98.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1voSU0-00000001QBb-0i2a
	for pgsql-hackers@lists.postgresql.org;
	Fri, 06 Feb 2026 20:31:18 +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 616KV3Rw1871493;
	Fri, 6 Feb 2026 15:31:03 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
cc: Thomas Munro <thomas.munro@gmail.com>,
        Jakub Wartak <jakub.wartak@enterprisedb.com>,
        Bruce Momjian <bruce@momjian.us>, Dimitrios Apostolou <jimis@gmx.net>,
        Magnus Hagander <magnus@hagander.net>, Tomas Vondra <tomas@vondra.me>,
        pgsql-hackers@lists.postgresql.org, Andres Freund <andres@anarazel.de>,
        Melanie Plageman <melanieplageman@gmail.com>,
        Heikki Linnakangas <hlinnaka@iki.fi>,
        Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
        David Rowley <dgrowleyml@gmail.com>
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files
In-reply-to: <643576b4-4ffd-4ffd-bc3e-dee4a3ab1eed@dunslane.net>
References: <4e46b377-cae1-09a8-49fa-634cfeb8bd20@gmx.net> <CABUevEx=CQcphH33TRcMeUkt-TZ=m+i1JhLHCdoB_FYE5ift2w@mail.gmail.com> <CA+hUKGL74G_CR50N+gr8N1E9emuFJMHAsEKr6oGmHZZDZjRJHg@mail.gmail.com> <CB08A202-4EC8-4192-8156-7F4CCFFC5A49@gmx.net> <CA+hUKGJQ=V4S-5Z=D6cDfsOz_7vGAAusj2b3fO36GuezcADamQ@mail.gmail.com> <CAKZiRmzF6SRR+AxPZsXzs1kaHrxjLO2sbLT4Q61EMA5PGQB3Vg@mail.gmail.com> <aQOZfXn95wahELr4@momjian.us> <CA+hUKGJbEp5fBfkS+J5OcrEzPTwugEtiusndiCx4gnN7HKfdpg@mail.gmail.com> <CAKZiRmzdvqtuZmrpUi-399gzko6xihDgCkJyTv--Sk4pgQ4x+g@mail.gmail.com> <CAKZiRmyDR5d7jdKdhL6TNKMtcY0fAaS-OQ3Bk3ZVejLZMrTCQw@mail.gmail.com> <CA+hUKG+cFFzRNqV=+XJOdtzkj0jDGfCjL6BLKtZ43css=_RFmw@mail.gmail.com> <CAKZiRmyrPZ+U5p39oaj3nfOtteoz4cA63pZTyE-2wVVOu! XuqKQ@mail.gmail.com> <CA+hUKGJ5AfAq-spM=b+KD0LNNXY-gAgaDDox9YFQZM+t8+je=g@mail.gmail.com> <1762439.1770390711@sss.pgh.pa.us> <e1f0cd3b-0164-45f5-9705-e922e59df90f@dunslane.net> <1802017.1770402662@sss.pgh.pa.us> <643576b4-4ffd-4ffd-bc3e-dee4a3ab1eed@d!
 unslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Fri, 06 Feb 2026 15:16:25 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1871491.1770409863.1@sss.pgh.pa.us>
Date: Fri, 06 Feb 2026 15:31:03 -0500
Message-ID: <1871492.1770409863@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/1871492.1770409863%40sss.pgh.pa.us>
Precedence: bulk

Andrew Dunstan <andrew@dunslane.net> writes:
> Fair enough. I agree it's not terribly helpful. In any case, maybe we 
> need to look at my earlier suggestion of adding a suppression file.

Perhaps, but since we're getting pretty hard up against the release
freeze deadline, I think the thing to do for today is just to update
.abi-compliance-history.  We know that way works.

			regards, tom lane