Re: [PING] fallocate() causes btrfs to never compress postgresql files
От | Dimitrios Apostolou |
---|---|
Тема | Re: [PING] fallocate() causes btrfs to never compress postgresql files |
Дата | |
Msg-id | 98daac7f-a351-def2-bc36-7538c996ff51@gmx.net обсуждение исходный текст |
Ответ на | [PING] fallocate() causes btrfs to never compress postgresql files (Dimitrios Apostolou <jimis@gmx.net>) |
Ответы |
Re: [PING] fallocate() causes btrfs to never compress postgresql files
|
Список | pgsql-hackers |
On Thu, 12 Jun 2025, Dimitrios Apostolou wrote: > On Mon, 9 Jun 2025, Thomas Munro wrote: > >> On Tue, Jun 3, 2025 at 1:58 AM Dimitrios Apostolou <jimis@gmx.net> wrote: >>> This sounds like the best solution IMO. People can then experiment with >>> different settings and filesystems, and that way we also learn in the >>> process. Thank you for the effort and patches so far. >> >> OK, here's a basic patch to experiment with. You can set: >> >> file_extend_method = fallocate,ftruncate,write >> file_extend_method_threshold = 8 # (below 8 always write, 0 means never >> write) >> > > I applied the patch on PostgreSQL v17 and am testing it now. I chose > ftruncate method and I see ftruncate in action using strace while doing > pg_restore of a big database. Nothing unexpected has happened so far. I also > verified that files are being compressed, obeying Btrfs's mount option > compress=zstd. > > Thanks for the patch! What are the odds of commiting it to v17? Ping. :-) Patch behaves good for me. Any chance of applying it and backporting it? > > Dimitris > >
В списке pgsql-hackers по дате отправления: