Re: New IndexAM API controlling index vacuum strategies

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Masahiko Sawada <sawada.mshk@gmail.com>

Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2021-01-20T01:14:25Z

Lists: pgsql-hackers

On Tue, Jan 19, 2021 at 4:45 PM Peter Geoghegan <pg@bowt.ie> wrote:
> BTW, I think that increasing MaxHeapTuplesPerPage will make it
> necessary to consider tidbitmap.c. Comments at the top of that file
> say that it is assumed that MaxHeapTuplesPerPage is about 256. So
> there is a risk of introducing performance regressions affecting
> bitmap scans here.

More concretely, WORDS_PER_PAGE increases from 5 on the master branch
to 16 with the latest version of the patch series on most platforms
(while WORDS_PER_CHUNK is 4 with or without the patches).

-- 
Peter Geoghegan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Don't truncate heap when VACUUM's failsafe is in effect.
- 60f1f09ff443 14.0 landed
Teach VACUUM to bypass unnecessary index vacuuming.
- 5100010ee4d5 14.0 landed
Add wraparound failsafe to VACUUM.
- 1e55e7d1755c 14.0 landed
Truncate line pointer array during VACUUM.
- 3c3b8a4b2689 14.0 landed
Remove tupgone special case from vacuumlazy.c.
- 8523492d4e34 14.0 landed
Refactor lazy_scan_heap() loop.
- 7ab96cf6b312 14.0 landed
Propagate parallel VACUUM's buffer access strategy.
- 49f49defe7c0 14.0 cited
Simplify state managed by VACUUM.
- b4af70cb2103 14.0 landed
Notice that heap page has dead items during VACUUM.
- 0ea71c93a06d 14.0 landed
Adjust lazy_scan_heap() accounting comments.
- 7cde6b13a9b6 14.0 cited
Use full 64-bit XID for checking if a deleted GiST page is old enough.
- 6655a7299d83 13.0 cited
Fix some problems with VACUUM (INDEX_CLEANUP FALSE).
- dd6959798885 12.0 cited