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

From: Floris Van Nee <florisvannee(at)Optiver(dot)com>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: non-HOT update not looking at FSM for large tuple update
Date: 2021-02-24 22:29:21
Message-ID: 7b2aac7964c142a79a07bd718691735e@opammb0562.comp.optiver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-02-24 23:19:52 Re: Some regular-expression performance hacking
Previous Message John Naylor 2021-02-24 21:50:50 Re: [POC] verifying UTF-8 using SIMD instructions