Re: Regarding fillfactor use case for only delete ops - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Regarding fillfactor use case for only delete ops
Date
Msg-id 84b6da7feb3de406d20a4a0e80954520a6db6b6c.camel@cybertec.at
Whole thread Raw
In response to Re: Regarding fillfactor use case for only delete ops  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Regarding fillfactor use case for only delete ops
List pgsql-general
On Fri, 2025-06-06 at 09:59 -0400, Ron Johnson wrote:
> On Fri, Jun 6, 2025 at 8:57 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> > On Fri, 2025-06-06 at 14:10 +0530, Durgamahesh Manne wrote:
> > > Can we generate a fill factor for tables that have delete ops ?
> > >
> > > Does the fill factor really work and help to minimize the bloat for tables that have delete ops?
> > >
> > > I have parent table with weekly partitions So for every week 50 to 60 gb of bloat generates and autovacuum params
alreadyin place for child tables  
> >
> > Nothing can ever avoid bloat caused by DELETE, except partitioning in a
> > way that you can drop a partition rather than running DELETE.
>
> Isn't the fill factor aimed at reducing bloat during updates of HOT tables?

Yes, but not during DELETEs.

HOT updates also don't directly avoid bloat on tables; only on indexes.
They reduce the bloat on tables inderectly, because the dead tuples can
be cleaned up with less effort.

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Andrus
Date:
Subject: How to use cert authentication with pg_dump in windows
Next
From: Ron Johnson
Date:
Subject: Re: Regarding fillfactor use case for only delete ops