Re: Crashes on a partition whose concurrent detach never finished - Mailing list pgsql-hackers

From Zsolt Parragi
Subject Re: Crashes on a partition whose concurrent detach never finished
Date
Msg-id CAN4CZFOxn6rv52YJRXE56sUx5iB-njB854o9jYLx2e-wO9hiAA@mail.gmail.com
Whole thread
In response to Re: Crashes on a partition whose concurrent detach never finished  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Crashes on a partition whose concurrent detach never finished
Re: Crashes on a partition whose concurrent detach never finished
List pgsql-hackers
Hello!

An automated claude review found a residual crash in pgoutput after
the committed fix, which repeatedly crashes the walsender following an
interrupted ALTER TABLE ... DETACH PARTITION ... CONCURRENTLY.

0001 contains a test case and a simple fix.

And after further looking, I realized that there's one more leftover
issue, which doesn't cause a crash but failures in subscribers:
pg_get_publication_tables only relied on relispartition instead of
following the same approach as the previous fix commit and 0001. 0002
modifies it to match the other locations.

Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Next
From: Alexandre Felipe
Date:
Subject: Re: aio: worker: Free SMGR objects when idle