Re: CREATE INDEX CONCURRENTLY on partitioned index - Mailing list pgsql-hackers

From Ilya Gladyshev
Subject Re: CREATE INDEX CONCURRENTLY on partitioned index
Date
Msg-id 5F602655-58E6-4562-85D3-34E04BE9D60C@gmail.com
Whole thread Raw
In response to Re: CREATE INDEX CONCURRENTLY on partitioned index  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: CREATE INDEX CONCURRENTLY on partitioned index
List 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




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Converting tab-complete.c's else-if chain to a switch
Next
From: Nathan Bossart
Date:
Subject: Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal