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+hUKGJ2yEsjjmq7GZLqT9bfuJjG1EPeqeapmW5RxroVpPThfA@mail.gmail.com
Whole thread
In response to Re: [PING] fallocate() causes btrfs to never compress postgresql files  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PING] fallocate() causes btrfs to never compress postgresql files
List pgsql-hackers
On Sat, Feb 7, 2026 at 9:31 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

So it seems I need to do the attached for 18, and the same again for
17 and 16.  Look about right?

I peeked at the libabigail man page, and I don't see any discussion of
incomplete types, but it looks like OPAQUE_TYPE_LABEL might be a way
to tell it about this.  If that works, wouldn't it be better than
doing this forever?  Where would that be configured?

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Decoupling our alignment assumptions about int64 and double
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD