Re: Parallel CREATE INDEX for GIN indexes

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Tomas Vondra <tomas.vondra@enterprisedb.com>

Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-10-08T02:03:34Z

Lists: pgsql-hackers

On Fri, Jul 12, 2024 at 05:34:25PM +0200, Tomas Vondra wrote:
> I got to do the detailed benchmarking on the latest version of the patch
> series, so here's the results. My goal was to better understand the
> impact of each patch individually - especially the two parts introduced
> by Matthias, but not only - so I ran the test on a build with each fo
> the 0001-0009 patches.

_gin_parallel_build_main() is introduced in 0001.  Please make sure to
pass down a query ID.
--
Michael

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