Re: CREATE INDEX CONCURRENTLY on partitioned index

From: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 李杰(慎追) <adger(dot)lj(at)alibaba-inc(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, 曾文旌(义从) <wenjing(dot)zwj(at)alibaba-inc(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: CREATE INDEX CONCURRENTLY on partitioned index
Date: 2022-06-29 06:45:49
Message-ID: 5f1d2d8f81dcd63f544af5ae61f881f9@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Pryzby писал 2022-06-28 21:33:
> Hi,
>
> On Thu, Feb 10, 2022 at 06:07:08PM +0300, Alexander Pyhalov wrote:
>> I've rebased patches and tried to fix issues I've seen. I've fixed
>> reference
>> after table_close() in the first patch (can be seen while building
>> with
>> CPPFLAGS='-DRELCACHE_FORCE_RELEASE').
>
> Thanks for finding that.
>
> The patches other than 0001 are more experimental, and need someone to
> check if
> it's even a good approach to use, so I kept them separate from the
> essential
> patch.
>
> Your latest 0005 patch (mark intermediate partitioned indexes as valid)
> is
> probably fixing a bug in my SKIPVALID patch, right ? I'm not sure
> whether the
> SKIPVALID patch should be merged into 0001, and I've been awaiting
> feedback on
> the main patch before handling progress reporting.

Hi. I think it's more about fixing ReindexPartitions-to-set-indisvalid
patch, as
we also should mark intermediate indexes as valid when reindex succeeds.

> Sorry for not responding sooner. The patch saw no activity for ~11
> months so I
> wasn't prepared to pick it up in March, at least not without guidance
> from a
> committer.
>
> Would you want to take over this patch ? I wrote it following
> someone's
> question, but don't expect that I'd use the feature myself. I can help
> review
> it or try to clarify the organization of my existing patches (but still
> haven't
> managed to work my way through your amendments to my patches).
>

Yes, I'm glad to work on the patches, as this for us this is a very
important feature.
--
Best regards,
Alexander Pyhalov,
Postgres Professional

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2022-06-29 06:51:10 Re: Hardening PostgreSQL via (optional) ban on local file system access
Previous Message Erik Rijkers 2022-06-29 06:12:03 Re: PostgreSQL 15 beta 2 release announcement draft