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-07-11T20:35:24Z
Lists: pgsql-hackers
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. > 11 июля 2024 г., в 13:31, Justin Pryzby <pryzby@telsasoft.com> написал(а): > > On Sat, Jun 15, 2024 at 07:56:38PM +0100, Ilya Gladyshev wrote: >> In addition, I noticed that progress tracking is once again broken for >> partitioned tables, while looking at REINDEX implementation, attaching the >> second patch to fix it. > > Thanks for the fixes, I started reviewing them but need some more time > to digest. > > Do you mean that progress reporting is broken in master, for REINDEX, or > just with this patch ? > > -- > Justin
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