| From: | Tomas Vondra <tomas(at)vondra(dot)me> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel CREATE INDEX for GIN indexes |
| Date: | 2025-03-03 16:16:34 |
| Message-ID: | eadbc612-c26a-4904-b94a-33e62b14689a@vondra.me |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v20250303-0001-Compress-TID-lists-when-writing-GIN-tuples.patch | text/x-patch | 8.2 KB |
| v20250303-0002-Enforce-memory-limit-during-parallel-GIN-b.patch | text/x-patch | 12.3 KB |
| v20250303-0003-Use-a-single-GIN-tuplesort.patch | text/x-patch | 32.2 KB |
| v20250303-0004-WIP-parallel-inserts-into-GIN-index.patch | text/x-patch | 18.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-03 16:18:46 | Re: bug when apply fast default mechanism for adding new column over domain with default value |
| Previous Message | Bertrand Drouvot | 2025-03-03 16:14:23 | Re: Log connection establishment timings |