| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Bráulio Oliveira <brauliobo(at)gmail(dot)com> |
| Cc: | Dimitrios Apostolou <jimis(at)gmx(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: fallocate() causes btrfs to never compress postgresql files |
| Date: | 2025-11-17 03:35:52 |
| Message-ID: | CA+hUKG+Lec=ht3VQKr964zP71oZBSfGrh5obzk49HiSff=7B_g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 17, 2025 at 4:23 PM Bráulio Oliveira <brauliobo(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tender Wang | 2025-11-17 03:36:48 | Re: Use opresulttype instead of calling SearchSysCache1() in match_orclause_to_indexcol() |
| Previous Message | Bráulio Oliveira | 2025-11-17 03:23:09 | Re: fallocate() causes btrfs to never compress postgresql files |