| From: | Ilya Gladyshev <ilya(dot)v(dot)gladyshev(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "李杰(慎追)" <adger(dot)lj(at)alibaba-inc(dot)com> |
| Subject: | Re: CREATE INDEX CONCURRENTLY on partitioned index |
| Date: | 2024-07-11 20:35:24 |
| Message-ID: | 5F602655-58E6-4562-85D3-34E04BE9D60C@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)telsasoft(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-07-11 20:42:26 | Re: Add a GUC check hook to ensure summarize_wal cannot be enabled when wal_level is minimal |
| Previous Message | Tom Lane | 2024-07-11 20:25:02 | Converting tab-complete.c's else-if chain to a switch |