Re: GiST VACUUM

x4mmm@yandex-team.ru

From: Andrey Borodin <x4mmm@yandex-team.ru>

To: Heikki Linnakangas <hlinnaka@iki.fi>

Cc: Robert Haas <robertmhaas@gmail.com>, Thomas Munro <thomas.munro@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Костя Кузнецов <chapaev28@ya.ru>

Date: 2018-07-23T18:04:57Z

Lists: pgsql-hackers

Attachments

0002-Delete-pages-during-GiST-VACUUM-v13.patch (application/octet-stream) patch v13-0002
0001-Physical-GiST-scan-in-VACUUM-v13.patch (application/octet-stream) patch v13-0001

Hi!

> 21 июля 2018 г., в 17:11, Andrey Borodin <x4mmm@yandex-team.ru> написал(а):
> 
> <0001-Physical-GiST-scan-in-VACUUM-v13.patch>

Just in case, here's second part of patch series with actual page deletion.

I was considering further decreasing memory footprint by using bloom filters instead of bitmap, but it will create seriously more work for cpu to compute hashes.

Best regards, Andrey Borodin.

Commits

Use full 64-bit XID for checking if a deleted GiST page is old enough.
- fb5344c969af 12.0 landed
- 6655a7299d83 13.0 landed
Refactor checks for deleted GiST pages.
- e2e992c93145 12.0 landed
- 9eb5607e6993 13.0 landed
Delete empty pages during GiST VACUUM.
- 7df159a620b7 12.0 landed
Scan GiST indexes in physical order during VACUUM.
- fe280694d0d4 12.0 landed
Prevent GIN deleted pages from being reclaimed too early
- 52ac6cd2d0cd 12.0 cited