| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Marcelo Fernandes <marcefern7(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Changing default fillfactor for the whole database |
| Date: | 2025-04-27 03:15:42 |
| Message-ID: | 55A52200-4335-4351-BDA4-604A860B24E9@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Apr 26, 2025, at 19:31, Marcelo Fernandes <marcefern7(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-04-27 03:30:24 | Re: Changing default fillfactor for the whole database |
| Previous Message | Marcelo Fernandes | 2025-04-27 02:31:19 | Changing default fillfactor for the whole database |