From: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com> |
---|---|
To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrey Borodin <amborodin86(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
Subject: | Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements |
Date: | 2024-12-09 20:53:00 |
Message-ID: | CANtu0ogTfyng-H4yWr3Pm_+PXX+XvDx1AM1sXTy1V7DM6jJ+Bw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, Matthias!
Added support for unique indexes.
So, now your initial idea about resetting during the first phase appears to
be ready.
Next step - use single-scan and auxiliary index for concurrent index build.
Also, I have updated the stress tests accordingly to [0].
Best regards,
Mikhail.
Attachment | Content-Type | Size |
---|---|---|
v5-0005-Allow-snapshot-resets-in-concurrent-unique-index-.patch | application/x-patch | 32.5 KB |
v5-0003-Allow-advancing-xmin-during-non-unique-non-parall.patch | application/x-patch | 35.8 KB |
v5-0001-this-is-https-commitfest.postgresql.org-50-5160-m.patch | application/x-patch | 61.5 KB |
v5-0002-Add-stress-tests-for-concurrent-index-operations.patch | application/x-patch | 20.2 KB |
v5-0004-Allow-snapshot-resets-during-parallel-concurrent-.patch | application/x-patch | 29.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2024-12-09 20:55:45 | Re: Refactoring postmaster's code to cleanup after child exit |
Previous Message | Michail Nikolaev | 2024-12-09 20:51:24 | bt_index_parent_check and concurrently build indexes |