Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u97Zl-00FfUZ-75 for pgsql-general@arkaria.postgresql.org; Sun, 27 Apr 2025 19:22:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u97Zj-00AJe6-6K for pgsql-general@arkaria.postgresql.org; Sun, 27 Apr 2025 19:22:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u97Zi-00AJdy-Rm for pgsql-general@lists.postgresql.org; Sun, 27 Apr 2025 19:22:03 +0000 Received: from smtp69.iad3b.emailsrvr.com ([146.20.161.69]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u97Zh-002Ftb-2H for pgsql-general@postgresql.org; Sun, 27 Apr 2025 19:22:02 +0000 X-Auth-ID: xof@thebuild.com Received: by smtp9.relay.iad3b.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 13713201B0; Sun, 27 Apr 2025 15:22:00 -0400 (EDT) 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 In-Reply-To: Date: Sun, 27 Apr 2025 12:21:30 -0700 Cc: pgsql-general Content-Transfer-Encoding: quoted-printable Message-Id: <042C320E-68B8-453E-A0DF-C1125A50C7A4@thebuild.com> References: To: Ron Johnson X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Classification-ID: 6b77c314-8f13-4d44-9dfd-3c1d1b891ef6-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Apr 27, 2025, at 06:54, Ron Johnson = wrote: >=20 > I agree with him, though, that this a foot-gun: most table's aren't = that UPDATE heavy.=20 There is plenty of precedent for GUCs that seem to be useful, but really = should never be touched except in the case of fairly uncommon workloads. = However, that doesn't mean we should add new ones. :-)=