public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Durgamahesh Manne <[email protected]>
To: Ron Johnson <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Regarding fillfactor use case for only delete ops
Date: Fri, 6 Jun 2025 16:14:27 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJCZkoKiRAjeCZKdEtZq054kdk0RpGF50gqwh7msLdogo5JOAw@mail.gmail.com>
References: <CAJCZkoLkMLsz1raz+XLJ09PUdgWv7mw37+zaFw9jNMhFUC+SVg@mail.gmail.com>
<[email protected]>
<CANzqJaB8aRCuEYYDU_qK0WUVVdWdoCte=wDt5387uj=Ncw5_Pg@mail.gmail.com>
<CAJCZkoKiRAjeCZKdEtZq054kdk0RpGF50gqwh7msLdogo5JOAw@mail.gmail.com>
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
[email protected]
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Regarding fillfactor use case for only delete ops
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox