Horton

RE: non-HOT update not looking at FSM for large tuple update

Floris Van Nee <florisvannee@optiver.com>

View thread View on postgr.es
From: Floris Van Nee <florisvannee@Optiver.com>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-02-24T22:29:21Z
Lists: pgsql-hackers 
> That makes sense, although the exact number seems precisely tailored to your use case. 2% gives 164 bytes of slack and doesn't seem too large. Updated patch attached.

Yeah, I tried picking it as conservative as I could, but 2% is obviously great too. :-) I can't think of any large drawbacks either of having a slightly larger value.
Thanks for posting the patch!

-Floris

Commits

  1. Accept slightly-filled pages for tuples larger than fillfactor.