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-19T10:52:34Z

Lists: pgsql-hackers

Attachments

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

Hi!

> 19 июля 2018 г., в 1:12, Heikki Linnakangas <hlinnaka@iki.fi> написал(а):
> 
> Yeah, please, I think this is the way to go.

Here's v11 divided into proposed steps.

In second step I still use paloc's memory, but only to store two bitmaps: bitmap of internal pages and bitmap of empty leafs. Second physical scan only reads internal pages. I can omit that bitmap, if I'll scan everything.
Also, I can replace emptyLeafs bitmap with array\list, but I do not really think it will be big.

Anyway I propose focusing on first step.

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