| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Regarding fillfactor use case for only delete ops |
| Date: | 2025-06-06 13:59:14 |
| Message-ID: | CANzqJaB8aRCuEYYDU_qK0WUVVdWdoCte=wDt5387uj=Ncw5_Pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-06-06 14:01:19 | Re: Regarding fillfactor use case for only delete ops |
| Previous Message | Laurenz Albe | 2025-06-06 12:57:02 | Re: Regarding fillfactor use case for only delete ops |