MIME-Version: 1.0
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Fri, 6 Jun 2025 14:10:46 +0530
Message-ID: <CAJCZkoLkMLsz1raz+XLJ09PUdgWv7mw37+zaFw9jNMhFUC+SVg@mail.gmail.com>
Subject: Regarding fillfactor use case for only delete ops
To: pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000008eeed50636e320ee"
Archived-At: <https://www.postgresql.org/message-id/CAJCZkoLkMLsz1raz%2BXLJ09PUdgWv7mw37%2BzaFw9jNMhFUC%2BSVg%40mail.gmail.com>
Precedence: bulk

--0000000000008eeed50636e320ee
Content-Type: text/plain; charset="UTF-8"

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


Regards,
Durga Mahesh

--0000000000008eeed50636e320ee
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi=C2=A0 Team<div><br></div><div>Can we generate a fill fa=
ctor for tables that have delete ops ?</div><div><br></div><div>Does the fi=
ll factor really work and help to minimize the bloat for tables that have d=
elete ops?</div><div><br></div><div>I have parent table with weekly partiti=
ons So for every week 50 to 60 gb of bloat generates and autovacuum params =
already in place for child tables=C2=A0</div><div><br></div><div><br></div>=
<div>Regards,</div><div>Durga Mahesh=C2=A0</div><div><br></div></div>

--0000000000008eeed50636e320ee--