From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Disabling Heap-Only Tuples |
Date: | 2023-08-30 13:01:36 |
Message-ID: | CAEze2Wjah_WQCGARwgJWsrmjaU09VKgEpVqBoFEomnCOperPTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 28 Aug 2023 at 17:57, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Mon, Aug 28, 2023 at 11:50 AM Matthias van de Meent
> <boekewurm+postgres(at)gmail(dot)com> wrote:
> > Agreed on all points. But isn't that true for most most tools on bloat
> > prevention and/or detection? E.g. fillfactor, autovacuum_*, ...
>
> Not nearly to the same extent, IMHO. A lot of those parameters can be
> left alone forever and you lose nothing. That's not so here.
I've reworked the patch a bit to remove the "excessive bloat with low
fillfactors when local space is available" issue that this parameter
could cause - local updates are now done if the selected page we would
be inserting into is after the old tuple's page and the old tuple's
page still (or: now) has space available.
Does that alleviate your concerns?
Kind regards,
Matthias van de Meent
Neon (https://neon.tech)
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Add-heap-reloption-local_update_limit.patch | application/octet-stream | 14.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2023-08-30 13:02:50 | Re: persist logical slots to disk during shutdown checkpoint |
Previous Message | Magnus Hagander | 2023-08-30 13:01:24 | Re: Commitfest manager for September |