Re: CREATE INDEX CONCURRENTLY on partitioned index
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Ilya Gladyshev <ilya.v.gladyshev@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Alexander Pyhalov <a.pyhalov@postgrespro.ru>, pgsql-hackers@lists.postgresql.org, Masahiko Sawada <sawada.mshk@gmail.com>, "李杰(慎追)" <adger.lj@alibaba-inc.com>
Date: 2024-07-12T00:01:30Z
Lists: pgsql-hackers
On Thu, Jul 11, 2024 at 09:35:24PM +0100, Ilya Gladyshev wrote: > It is broken in master, I just didn’t want to create a separate > thread, but it can be fixed independently. As I remember, the > problem is that progress is tracked for each table in the hierarchy > as if the table is processed separately, without ever setting > partitions_total and partitions_done counters. Please let's move this point to its own thread and deal with it with an independent patch. Hiding that in a thread that's already quite long is not a good idea. This needs proper review, and a separate thread with a good subject to describe the problem will attract a better audience to deal with the problem you are seeing. I was not paying much attention, until you've mentioned that this was an issue with HEAD. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix assertion failure with REINDEX and event triggers
- c426f7c2b36a 17.0 cited