RE: Fix apply worker crash when subscriber table has only a deferrable primary key

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Nisha Moond' <nisha(dot)moond412(at)gmail(dot)com>, Zhijie Hou <houzhijie22(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: Fix apply worker crash when subscriber table has only a deferrable primary key
Date: 2026-10-06 02:56:17
Message-ID: OS7PR01MB183177937497570C7257C56EFF5952@OS7PR01MB18317.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Nisha,

> I’ve also updated the commit message to describe the new approach.
>
> v5-001 applies cleanly on PG19 and PG18, but not on PG17. Attached a
> separate PG17 patch.

Thanks for the patch. I locally tested with partitioned tables, and it worked
well. I have no comments.

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2026-10-06 03:08:06 Re: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)
Previous Message Fujii Masao 2026-10-06 02:50:04 Re: REPACK (CONCURRENTLY) might keep dropped-column data