Re: Three more loops that let a function drop a not-yet-processed index/partition

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Three more loops that let a function drop a not-yet-processed index/partition
Date: 2026-11-21 03:04:23
Message-ID: awEKNwq2b8dOyaVJ@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 20, 2026 at 07:00:49PM -0600, Baji Shaik wrote:
> While looking at d94964f14f39, I noticed a similar issue in a couple of
> other
> code paths which fail with "could not open relation with OID ..." or a
> cache lookup failure. This happens in plain REINDEX TABLE

Yep. I was aware of this one already, just did not get down to look
at how to fix it in more details. At quick glance, that seems
sensible. Thanks for the patch.

> CREATE INDEX on
> a partitioned table, and ALTER TABLE ... ATTACH PARTITION.

I have not looked at these two.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-11-21 03:06:06 Re: Checkpoints stuck after a failed bulk write inside a savepoint
Previous Message Tomás Senart 2026-11-21 02:53:43 Re: [PATCH v1] Match jsonpath variable names exactly when checking mutability