Re: [PING] fallocate() causes btrfs to never compress postgresql files - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [PING] fallocate() causes btrfs to never compress postgresql files
Date
Msg-id CA+hUKGJ5AfAq-spM=b+KD0LNNXY-gAgaDDox9YFQZM+t8+je=g@mail.gmail.com
Whole thread Raw
In response to Re: [PING] fallocate() causes btrfs to never compress postgresql files  (Jakub Wartak <jakub.wartak@enterprisedb.com>)
List pgsql-hackers
On Fri, Feb 6, 2026 at 8:19 PM Jakub Wartak
<jakub.wartak@enterprisedb.com> wrote:
> On Fri, Feb 6, 2026 at 6:12 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> > On Mon, Jan 12, 2026 at 11:04 PM Jakub Wartak
> > <jakub.wartak@enterprisedb.com> wrote:
> > > > > I'm proposing to back-patch 0001.  0002 and 0003 are proposals for master only.
> >
> > > Do you have any plans to commit this before February (before next
> > > minor release) or perhaps do you need some further input or help in
> > > this $thread? (I'm mainly after the XFS thingy, but we kill two birds
> > > with 1 stone here).
> >
> > Pushed.
>
> Thank You very much !

BTW the rest of the patches will reemerge for master, but for the
minimal one back-patched: crake complains about an ABI break due to
GUC table changes.  Of course adding a GUC to the stable branches is
unusual and we discussed the need for it in this case.  Is that
expected?  In what way is it part of the ABI?  How would one determine
in advance that the ABI checker will complain?



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: Add expressions to pg_restore_extended_stats()
Next
From: "Jelte Fennema-Nio"
Date:
Subject: Re: meson: Make test output much more useful on failure (both in CI and locally)