| 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-10-24 00:29:36 |
| Message-ID: | 179280177691.3657984.6447159513136213847@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Ajit,
On Mon, Oct 19, 2026 at 11:17 AM Ajit Awekar <ajitpostgres(at)gmail(dot)com>
wrote:
> Only setrefs.c needed manual changes; there is no functional change
> from V3.
I applied V4 to today's master (126976a8ffc). It still applies
cleanly, builds with --enable-cassert without warnings, and make check
and postgres_fdw's check pass. The eight cases from my V3 review give
output byte-identical to V3: the original case, the dropped and renamed
columns with triggers, the mixed partitions and the self-join return
the right rows; the chained case still updates the wrong rows, as
documented.
Regards,
Manu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-10-24 01:02:19 | Re: [PATCH v1 1/1] Add GENERATED ALWAYS AS ROW IDENTITY columns |
| Previous Message | Manu | 2026-10-24 00:21:17 | Re: Parallel vacuum: workers together with leader could overrun cost budget |