Re: Regarding fillfactor use case for only delete ops

From: Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Regarding fillfactor use case for only delete ops
Date: 2025-06-06 23:04:21
Message-ID: CAJCZkoKiRAjeCZKdEtZq054kdk0RpGF50gqwh7msLdogo5JOAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jun 6, 2025 at 7:29 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> On Fri, Jun 6, 2025 at 8:57 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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 already in 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.
>>
>>
> Laurenz,
>
> Isn't the fill factor aimed at reducing bloat during updates of HOT tables?
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>

Hi

I believe that fill factor works exclusively for updates of HOT tables but
not for delete ops

Regards,
Durga Mahesh

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Durgamahesh Manne 2025-06-06 23:09:20 Re: Regarding fillfactor use case for only delete ops
Previous Message Tom Lane 2025-06-06 14:32:11 Re: Low OIDs (< 16384) when creating databases in single user mode