Re: Regarding fillfactor use case for only delete ops

On 6/6/25 16:04, Durgamahesh Manne wrote:
>

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

From here:

https://www.postgresql.org/docs/current/sql-createtable.html

"fillfactor (integer)

The fillfactor for a table is a percentage between 10 and 100. 100
(complete packing) is the default. When a smaller fillfactor is
specified, INSERT operations pack table pages only to the indicated
percentage; the remaining space on each page is reserved for updating
rows on that page. This gives UPDATE a chance to place the updated copy
of a row on the same page as the original, which is more efficient than
placing it on a different page, and makes heap-only tuple updates more
likely. For a table whose entries are never updated, complete packing is
the best choice, but in heavily updated tables smaller fillfactors are
appropriate. This parameter cannot be set for TOAST tables.
"

So it increases the chances of HOT updates, but is not restricted to them.

>
> Regards,
> Durga Mahesh
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com