Re: CREATE INDEX CONCURRENTLY on partitioned index

Ilya Gladyshev <ilya.v.gladyshev@gmail.com>

From: Ilya Gladyshev <ilya.v.gladyshev@gmail.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alexander Pyhalov <a.pyhalov@postgrespro.ru>, pgsql-hackers@lists.postgresql.org, Masahiko Sawada <sawada.mshk@gmail.com>, Michael Paquier <michael@paquier.xyz>, 李杰(慎追) <adger.lj@alibaba-inc.com>
Date: 2024-06-20T19:20:58Z
Lists: pgsql-hackers

Attachments

On 15.06.2024 20:40, Justin Pryzby wrote:
> On Thu, May 23, 2024 at 10:14:57PM +0100, Ilya Gladyshev wrote:
>> Hi,
>>
>> I think it's well worth the effort to revive the patch, so I rebased it on
>> master, updated it and will return it back to the commitfest. Alexander,
>> Justin feel free to add yourselves as authors
> Thanks -- I was intending to write about this.
>
> I realized that the patch will need some isolation tests to exercise its
> concurrent behavior.


Thanks for the suggestion, added an isolation test that verifies 
behaviour of partitioned CIC with simultaneous partition drop/detach 
going on. Also fixed some issues in the new patch that I found while 
writing the test.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix assertion failure with REINDEX and event triggers