Re: New IndexAM API controlling index vacuum strategies

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>
Subject: Re: New IndexAM API controlling index vacuum strategies
Date: 2021-03-31 03:01:27
Message-ID: CAH2-Wz=v_YVfgMvZ-BpxxmtzW=D1fFT4YAHcM3m=jeQcSwyBxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 28, 2021 at 9:16 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> And now here's v8, which has the following additional cleanup:

And here's v9, which has improved commit messages for the first 2
patches, and many small tweaks within all 4 patches.

The most interesting change is that lazy_scan_heap() now has a fairly
elaborate assertion that verifies that its idea about whether or not
the page is all_visible and all_frozen is shared by
heap_page_is_all_visible() -- this is a stripped down version of the
logic that now lives in lazy_scan_heap(). It exists so that the second
pass over the heap can set visibility map bits.

--
Peter Geoghegan

Attachment Content-Type Size
v9-0001-Simplify-state-managed-by-VACUUM.patch application/octet-stream 116.4 KB
v9-0003-Remove-tupgone-special-case-from-vacuumlazy.c.patch application/octet-stream 43.7 KB
v9-0004-Bypass-index-vacuuming-in-some-cases.patch application/octet-stream 26.9 KB
v9-0002-Refactor-lazy_scan_heap.patch application/octet-stream 66.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2021-03-31 03:01:55 Re: What to call an executor node which lazily caches tuples in a hash table?
Previous Message Tom Lane 2021-03-31 02:56:08 Re: making update/delete of inheritance trees scale better