Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements

Mihail Nikalayeu <michail.nikolaev@gmail.com>

From: Michail Nikolaev <michail.nikolaev@gmail.com>

To: Matthias van de Meent <boekewurm+postgres@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andrey Borodin <amborodin86@gmail.com>, Melanie Plageman <melanieplageman@gmail.com>

Date: 2024-12-09T20:53:00Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Revert changes to CONCURRENTLY that "sped up" Xmin advance
- e28bb8851969 15.0 cited
VACUUM: ignore indexing operations with CONCURRENTLY
- d9d076222f5b 14.0 cited
Avoid spurious waits in concurrent indexing
- c98763bf51bf 14.0 cited

Attachments

v5-0005-Allow-snapshot-resets-in-concurrent-unique-index-.patch (application/x-patch) patch v5-0005
v5-0003-Allow-advancing-xmin-during-non-unique-non-parall.patch (application/x-patch) patch v5-0003
v5-0001-this-is-https-commitfest.postgresql.org-50-5160-m.patch (application/x-patch) patch v5-0001
v5-0002-Add-stress-tests-for-concurrent-index-operations.patch (application/x-patch) patch v5-0002
v5-0004-Allow-snapshot-resets-during-parallel-concurrent-.patch (application/x-patch) patch v5-0004

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].

[0]:
https://www.postgresql.org/message-id/flat/CANtu0ojmVd27fEhfpST7RG2KZvwkX%3DdMyKUqg0KM87FkOSdz8Q%40mail.gmail.com

Best regards,
Mikhail.