Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements

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-17 23:29:13
Message-ID: CANtu0oi+nbipJUsMZcoUfodCyuTN_DAXD22UstjMTYWG=tJ4jw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello!

After [0] fix, I simplified stress tests to single pgbench run without any
forks.

[0]: https://commitfest.postgresql.org/51/5439/

>

Attachment Content-Type Size
v6-0005-Allow-snapshot-resets-during-parallel-concurrent-.patch application/octet-stream 29.2 KB
v6-0004-Allow-advancing-xmin-during-non-unique-non-parall.patch application/octet-stream 35.8 KB
v6-0002-this-is-https-commitfest.postgresql.org-50-5160-m.patch application/octet-stream 61.5 KB
v6-0003-Add-stress-tests-for-concurrent-index-operations.patch application/octet-stream 6.5 KB
v6-0006-Allow-snapshot-resets-in-concurrent-unique-index-.patch application/octet-stream 32.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2024-12-17 23:56:09 Final result (display) collation?
Previous Message Heikki Linnakangas 2024-12-17 23:24:48 Re: Exceptional md.c paths for recovery and zero_damaged_pages