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

From Thomas Munro
Subject Re: fallocate() causes btrfs to never compress postgresql files
Date
Msg-id CA+hUKG+Lec=ht3VQKr964zP71oZBSfGrh5obzk49HiSff=7B_g@mail.gmail.com
Whole thread Raw
In response to Re: fallocate() causes btrfs to never compress postgresql files  (Bráulio Oliveira <brauliobo@gmail.com>)
List pgsql-hackers
On Mon, Nov 17, 2025 at 4:23 PM Bráulio Oliveira <brauliobo@gmail.com> wrote:
> Are there any plans to merge the file_extend_method soon? BTRFS
> compressed the original
> database to 36% of the original size, but now with the DB running it is using
> a lot of space crazily, not sure if running VACUUM and ANALYSE is
> making things worse.

Yeah, I'm planning to post a version with documentation and responses
to the new feedback on that thread soon.  Sorry it didn't make last
week's release.



pgsql-hackers by date:

Previous
From: Bráulio Oliveira
Date:
Subject: Re: fallocate() causes btrfs to never compress postgresql files
Next
From: Tender Wang
Date:
Subject: Re: Use opresulttype instead of calling SearchSysCache1() in match_orclause_to_indexcol()