Re: pgsql: Allow parallel CREATE INDEX for GIN indexes

2025-04-02 Thread Tomas Vondra
On 4/1/25 15:30, Peter Eisentraut wrote: > On 07.03.25 22:22, Peter Eisentraut wrote: >> The new tuplesort_getgintuple() in tuplesortvariants.c has a branch >> that does "return false" even though the function's return type is >> GinTuple *.  That is probably a mistake.  Check please. >> >> Also, t

Re: pgsql: Allow parallel CREATE INDEX for GIN indexes

2025-04-01 Thread Peter Eisentraut
On 07.03.25 22:22, Peter Eisentraut wrote: The new tuplesort_getgintuple() in tuplesortvariants.c has a branch that does "return false" even though the function's return type is GinTuple *.  That is probably a mistake.  Check please. Also, this code contains a "pgrminclude ignore", but we don'

Re: pgsql: Allow parallel CREATE INDEX for GIN indexes

2025-03-07 Thread Peter Eisentraut
The new tuplesort_getgintuple() in tuplesortvariants.c has a branch that does "return false" even though the function's return type is GinTuple *. That is probably a mistake. Check please. Also, this code contains a "pgrminclude ignore", but we don't use those anymore. On 03.03.25 17:10,

pgsql: Allow parallel CREATE INDEX for GIN indexes

2025-03-03 Thread Tomas Vondra
Allow parallel CREATE INDEX for GIN indexes Allow using parallel workers to build a GIN index, similarly to BTREE and BRIN. For large tables this may result in significant speedup when the build is CPU-bound. The work is divided so that each worker builds index entries on a subset of the table, d