Re: [PATCH] Fix: Partitioned parent index remains invalid after child indexes are repaired

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Haibo Yan <tristan(dot)yim(at)gmail(dot)com>, Mohamed ALi <moali(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix: Partitioned parent index remains invalid after child indexes are repaired
Date: 2026-04-18 14:37:48
Message-ID: CAA5RZ0uM7_YPdSahGh1sGeewMb9SzKswyLaZty8aR+a7XpQydQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> Could you write a patch? It would be better to have tests with
> multiple levels, at least, with a partitioned table being a leaf of
> another partitioned table. I am sure you get the picture, the point
> being to recurse across multiple levels.

Here is the patch with tests. It adds a test for this case using
multi-level partitions and ensures that the parent indexes are
validated once a child index is set to valid. Also, I added the
negative case where only one child index is validated to ensure
that the parent indexes remain invalid.

--
Sami Imseih
Amazon Web Services (AWS)

Attachment Content-Type Size
v1-0001-Allow-ALTER-INDEX-ATTACH-PARTITION-to-validate-th.patch application/octet-stream 8.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-04-18 15:00:00 Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Previous Message Mihail Nikalayeu 2026-04-18 13:33:00 Re: Resetting snapshots during the first phase of [CREATE |RE]INDEX CONCURRENTLY