pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Dimitrios Apostolou <jimis@gmx.net>
Cc: Tomas Vondra <tomas@vondra.me>
Cc: pgsql-hackers@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Cc: Melanie Plageman <melanieplageman@gmail.com>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: John Naylor <john.naylor@enterprisedb.com>
Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files
Date: Sat, 31 May 2025 11:42:01 -0400
Message-ID: <2818249.1748706121@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+hUKGJeO8xF5JBiRwc5onCrmthkhoeY0RC538v5vLd7c4s_LQ@mail.gmail.com>
References: <b1843124-fd22-e279-a31f-252dffb6fbf2@gmx.net>
	<9d1b371b-c395-422c-8ecc-ff6b48dfa793@vondra.me>
	<4aa3d83d-9630-61ac-85a7-a55490be49a6@gmx.net>
	<CA+hUKGJeO8xF5JBiRwc5onCrmthkhoeY0RC538v5vLd7c4s_LQ@mail.gmail.com>

Thomas Munro <thomas.munro@gmail.com> writes:
> It's slightly tricky to get smgr to behave differently because of the
> contents of a system catalogue!

The mere thought makes me blanch.  I'm okay with the GUC part,
but I do not think we should put in 0002 --- the odds of
causing serious problems greatly outweigh the value, IMO.
Fundamental layering violations tend to bite you on tender
parts of your anatomy.

			regards, tom lane





view thread (43+ messages)  latest in thread

Message-ID: <2818249.1748706121@sss.pgh.pa.us>
Permalink:  ../2818249.1748706121@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2818249.1748706121@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, jimis@gmx.net, tomas@vondra.me, andres@anarazel.de, melanieplageman@gmail.com, hlinnaka@iki.fi, horikyota.ntt@gmail.com, dgrowleyml@gmail.com, john.naylor@enterprisedb.com
  Subject: Re: [PING] fallocate() causes btrfs to never compress postgresql files
  In-Reply-To: <2818249.1748706121@sss.pgh.pa.us>
  References: <b1843124-fd22-e279-a31f-252dffb6fbf2@gmx.net> <9d1b371b-c395-422c-8ecc-ff6b48dfa793@vondra.me> <4aa3d83d-9630-61ac-85a7-a55490be49a6@gmx.net> <CA+hUKGJeO8xF5JBiRwc5onCrmthkhoeY0RC538v5vLd7c4s_LQ@mail.gmail.com> <2818249.1748706121@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox