| From: | Manu <manuelreyesbravo(at)gmail(dot)com> |
|---|---|
| To: | Ajit Awekar <ajitpostgres(at)gmail(dot)com> |
| Cc: | Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, shihao zhong <zhong950419(at)gmail(dot)com>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, rhaas(at)postgresql(dot)org |
| Subject: | Re: [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table |
| Date: | 2026-11-03 12:48:08 |
| Message-ID: | 179371008812.1245613.18345043610354071644@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Ajit,
On Tue, Nov 3, 2026 at 6:59 AM Ajit Awekar <ajitpostgres(at)gmail(dot)com>
wrote:
> I added regression tests for 1 and 2. Manu's case_i_whole_row.sql
> (i1-i8) runs without errors on v5, with the same results as master.
Confirmed on master 3ba886b35a2 with cassert: v5 builds without
warnings, make check and postgres_fdw's check pass, and
case_i_whole_row returns the same rows as master; only the plans
differ. Through a single foreign table the duplicate-ctid UPDATEs and
DELETEs now hit the right rows (7 of 7, master 0 of 7), and the
chained case is unchanged, as the docs now say.
I've set the entry to Ready for Committer.
Regards,
Manu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafia Sabih | 2026-11-03 13:24:53 | Re: Bypassing cursors in postgres_fdw to enable parallel plans |
| Previous Message | Shlok Kyal | 2026-11-03 12:37:19 | Re: Per-table resync for logical replication subscriptions |