Re: Parallel CREATE INDEX for GIN indexes

Tomas Vondra <tomas@vondra.me>

From: Tomas Vondra <tomas@vondra.me>

To: Matthias van de Meent <boekewurm+postgres@gmail.com>

Cc: Kirill Reshke <reshkekirill@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-03-03T16:16:34Z

Lists: pgsql-hackers

Attachments

v20250303-0001-Compress-TID-lists-when-writing-GIN-tuples.patch (text/x-patch) patch v20250303-0001
v20250303-0002-Enforce-memory-limit-during-parallel-GIN-b.patch (text/x-patch) patch v20250303-0002
v20250303-0003-Use-a-single-GIN-tuplesort.patch (text/x-patch) patch v20250303-0003
v20250303-0004-WIP-parallel-inserts-into-GIN-index.patch (text/x-patch) patch v20250303-0004

I've pushed the first part of the series (0001 + the cleanup and
progress patch). That leaves the two smaller improvement parts
(compression + memory limit enforcement) - I intend to push those
sometime this week, if possible.

Here's a rebased version of the whole patch series, including the two
WIP parts that are unlikely to make it into PG18 at this point.

regards

-- 
Tomas Vondra

Commits

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

Exercise parallel GIN builds in regression tests
- f6e5d21bf73f 19 (unreleased) landed
- 32593394ee43 18.2 landed
Lookup the correct ordering for parallel GIN builds
- db14dcdec69d 19 (unreleased) landed
- eee71a66cc86 18.2 landed
Fix memory leak in _gin_parallel_merge
- 1681a70df3d6 18.0 landed
Enforce memory limit during parallel GIN builds
- b229c1016477 18.0 landed
Compress TID lists when writing GIN tuples to disk
- 0b2a45a5d1f2 18.0 landed
Allow parallel CREATE INDEX for GIN indexes
- 8492feb98f6d 18.0 landed