Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Subject: Re: Changing default fillfactor for the whole database
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <CAM2F1VMu747bv5X3wTvhzLQUWRaJzREdaS=coVz+WjxkBjzvng@mail.gmail.com>
Date: Sat, 26 Apr 2025 20:15:42 -0700
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <55A52200-4335-4351-BDA4-604A860B24E9@thebuild.com>
References: <CAM2F1VMu747bv5X3wTvhzLQUWRaJzREdaS=coVz+WjxkBjzvng@mail.gmail.com>
To: Marcelo Fernandes <marcefern7@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/55A52200-4335-4351-BDA4-604A860B24E9%40thebuild.com>
Precedence: bulk


> On Apr 26, 2025, at 19:31, Marcelo Fernandes <marcefern7@gmail.com> =
wrote:
> Does this make sense? Have I missed something about being able to =
change this
> on a database level?

You haven't missed anything; there's no setting that controls the =
default for fillfactor.

Everyone's use-case is different, of course, but my feeling is that a =
correct fillfactor is very sensitive to the insert/update pattern for a =
particular table, so I'm not sure it makes sense to have a system-wide =
default.  I can certainly see it being a foot-gun, in setting it to =
(say) 50 and then some months later creating a table that is going to =
get very large, but is not update-heavy.=