Re: Crashes on a partition whose concurrent detach never finished

From: Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>
To: shveta malik <shveta(dot)malik(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, ashutosh(dot)bapat(dot)oss(at)gmail(dot)com
Subject: Re: Crashes on a partition whose concurrent detach never finished
Date: 2026-09-10 14:10:27
Message-ID: CABdArM7LhFa8SyoSSOcgvSZJeG82JLHk4KY_r+CAJQTBPz0S7g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 10, 2026 at 5:37 PM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
> > ~~~
> >
> > Given that we are treating a detach-pending partition as an individual
> > table for publication decisions, the changes in patch-003 (pg19
> > regression) look correct to me. The changes in relcache.c correctly
> > treat the detach-pending partition as an individual table.
> >
>
> I haven't had a chance to reveiw 003 yet as 001 itself was
> problematic. Will review it tomorrow.
>

Here is a rebased version of 003 that applies independently on both
HEAD and pg19. This should make reviewing patch-003 separately easier.

--
Thanks,
Nisha

Attachment Content-Type Size
v2_003-0001-Fix-crash-on-UPDATE-or-DELETE-of-a-partition-.patch application/octet-stream 5.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-09-10 14:10:30 Re: Trying out <stdatomic.h>
Previous Message Andres Freund 2026-09-10 14:07:02 FOR PORTION OF code review