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+hUKGKGgDOdS=n77p1=VUf5=XV2=L7VSiZW99Re7kUTRGMgxQ@mail.gmail.com
Whole thread Raw
In response to Re: [PING] fallocate() causes btrfs to never compress postgresql files  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Tue, Jul 29, 2025 at 6:52 PM Magnus Hagander <magnus@hagander.net> wrote:
> Not just to throw a wrench in there, but... Should this perhaps be a tablespace option? ISTM having different
filesystemsfor them is a good reason to use tablespaces in the first place, and then being able to pick different
options...

We discussed that a bit earlier in the thread.  Some problems about
layering violations and general weirdness, I recall trying it even.
On the flip side, is it right to declare very local
filesystem-specific choices in a system catalogue that is replicated
and affects replicas?
What about a fancier GUC that can reference tablespaces?



pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Showing applied extended statistics in explain Part 2
Next
From: Nikita Malakhov
Date:
Subject: Re: Dead code with short varlenas in toast_save_datum()