From: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Regarding fillfactor use case for only delete ops |
Date: | 2025-06-06 23:09:20 |
Message-ID: | CAJCZkoJ09T3YN2duJAQC1GH6yn9zxF06azRb_C5DGnKyAGPgPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 6, 2025 at 7:31 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> On Fri, Jun 6, 2025 at 4:36 AM Durgamahesh Manne <
> maheshpostgres9(at)gmail(dot)com> wrote:
>
>> Hi Team
>>
>> 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
>>
>
> This confuses me. It seems that you are deleting old data instead of just
> dropping the old partitions.
>
> What did I misunderstand?
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
>
Hi
I have partitioned table with retention policy of 90 days and will be auto
purged partitions beyond 90 days and for last 90 days tables inserts and
deletes usually run through apl call
Here due to deletes ops on last 90 days weekly partitions bloat generates
50gb to 60gb for on weekly partition even we set autovacuum params already
in place for at child tables level
Regards,
Durga Mahesh
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2025-06-06 23:14:27 | Re: Regarding fillfactor use case for only delete ops |
Previous Message | Durgamahesh Manne | 2025-06-06 23:04:21 | Re: Regarding fillfactor use case for only delete ops |