Re: Parallel CREATE INDEX for GIN indexes

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Tomas Vondra <tomas@vondra.me>, Matthias van de Meent <boekewurm+postgres@gmail.com>, Kirill Reshke <reshkekirill@gmail.com>, Michael Paquier <michael@paquier.xyz>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-03-09T22:27:53Z

Lists: pgsql-hackers

On Sun, Mar 9, 2025 at 6:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Ah.  Most likely somebody dismissed it years ago.  Given that
> precedent, I'm content to dismiss this one too.

It is dead code, unless somebody decides to #define
DISABLE_LEADER_PARTICIPATION to debug a problem.

-- 
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 →

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