Re: Changing default fillfactor for the whole database

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Changing default fillfactor for the whole database
Date: 2025-04-27 19:21:30
Message-ID: 042C320E-68B8-453E-A0DF-C1125A50C7A4@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Apr 27, 2025, at 06:54, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
> I agree with him, though, that this a foot-gun: most table's aren't that UPDATE heavy.

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. :-)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marcelo Fernandes 2025-04-27 23:28:41 Resetting the lock_timeout value for a transaction
Previous Message Ron Johnson 2025-04-27 13:54:24 Re: Changing default fillfactor for the whole database