| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(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" <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: Crashes on a partition whose concurrent detach never finished |
| Date: | 2026-09-21 21:01:33 |
| Message-ID: | CAN4CZFOxn6rv52YJRXE56sUx5iB-njB854o9jYLx2e-wO9hiAA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| 0001-Fix-crash-in-pgoutput-when-decoding-a-partition-pend.patch | application/octet-stream | 6.2 KB |
| 0002-Fix-publication-table-list-for-a-partition-pending-d.patch | application/octet-stream | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandre Felipe | 2026-09-21 21:15:18 | Re: aio: worker: Free SMGR objects when idle |
| Previous Message | Bharath Rupireddy | 2026-09-21 20:59:45 | Re: [PATCH] Release replication slot on error in SQL-callable slot functions |