| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| Cc: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [(known) BUG] DELETE/UPDATE more than one row in partitioned foreign table |
| Date: | 2026-05-14 15:05:41 |
| Message-ID: | CAN-LCVM2iOWkfFt22yVEGOrp-76YP3-BVKQg+A20TENkVh8o1w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi hackers!
I've rebased the patch set and created patch in current commitfest.
Reviewers are welcome!
Current Postgres copy slot/tuple mechanics supports only the case where
source and destination
slot/tuple have an equal number of attributes. To support additional remote
OID attribute
I've extended these functions to be able to work when source and
destination differ.
The second patch - core-remote-tableoid-param - introduces remote table OID
and
passes it through the executor to be used by the FDW engine.
The third patch teaches FDW engine to use this remote table OID in UPDATE
and
DELETE queries.
CF entry: https://commitfest.postgresql.org/patch/6770/
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0002-core-remote-tableoid-param.patch | application/octet-stream | 17.3 KB |
| v2-0001-copy-slot-tuple-natts.patch | application/octet-stream | 25.0 KB |
| v2-0003-teach-fdw-use-remote-tableoid.patch | application/octet-stream | 93.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2026-05-14 15:30:46 | Re: [SQL/PGQ] Early pruning for GRAPH_TABLE path generation |
| Previous Message | Fujii Masao | 2026-05-14 14:30:13 | postgres_fdw: restore_stats uses current user's mapping instead of table owner's during ANALYZE |