On Sun, 2021-07-18 at 09:36 +0200, Tobias Gierke wrote:
> Thank you for the detailed explanation ! Just one more question: I've
> did an experiment and reduced the fillfactor on the table updated by the
> trigger to 50%, hoping the HOT feature would kick in and each
> subsequent INSERT would clean up the "HOT chain" of the previous INSERT
> ... but execution times did not change at all compared to 100%
> fillfactor, why is this ? Does the HOT feature only work if a different
> backend accesses the table concurrently ?
No, but until the transaction is done, the tuples cannot be removed,
no matter if they are HOT or not.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com