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-17T23:29:13Z
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
- v6-0005-Allow-snapshot-resets-during-parallel-concurrent-.patch (application/octet-stream) patch v6-0005
- v6-0004-Allow-advancing-xmin-during-non-unique-non-parall.patch (application/octet-stream) patch v6-0004
- v6-0002-this-is-https-commitfest.postgresql.org-50-5160-m.patch (application/octet-stream) patch v6-0002
- v6-0003-Add-stress-tests-for-concurrent-index-operations.patch (application/octet-stream) patch v6-0003
- v6-0006-Allow-snapshot-resets-in-concurrent-unique-index-.patch (application/octet-stream) patch v6-0006
Hello! After [0] fix, I simplified stress tests to single pgbench run without any forks. [0]: https://commitfest.postgresql.org/51/5439/ >