| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Dimitrios Apostolou <jimis(at)gmx(dot)net>, Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: [PING] fallocate() causes btrfs to never compress postgresql files |
| Date: | 2025-08-05 13:07:57 |
| Message-ID: | CA+hUKGKGgDOdS=n77p1=VUf5=XV2=L7VSiZW99Re7kUTRGMgxQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 29, 2025 at 6:52 PM Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Not just to throw a wrench in there, but... Should this perhaps be a tablespace option? ISTM having different filesystems for 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikita Malakhov | 2025-08-05 13:14:35 | Re: Dead code with short varlenas in toast_save_datum() |
| Previous Message | Álvaro Herrera | 2025-08-05 12:34:03 | Re: Showing applied extended statistics in explain Part 2 |