Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>,
Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>,
Dilip Kumar <dilipbalaut@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Robert Haas <robertmhaas@gmail.com>
Date: 2017-11-26T22:56:32Z
Lists: pgsql-hackers
Attachments
- fix-rewrite-tlist-v5.patch (text/x-diff) patch v5
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> writes: > [ fix-rewrite-tlist-v4.patch ] I started reviewing this patch. I did not much like the fact that it effectively moved rewriteTargetListUD to a different file and renamed it. That seems like unnecessary code churn, plus it breaks the analogy with rewriteTargetListIU, plus it will make back-patching harder (since that code isn't exactly the same in back branches). I see little reason why we can't leave it where it is and just make it non-static. It's not like there's no other parts of the rewriter that the planner calls. I revised the patch along that line, and while at it, refactored preptlist.c a bit to eliminate repeated heap_opens of the target relation. I've not really reviewed any other aspects of the patch yet, but in the meantime, does anyone object to proceeding this way? regards, tom lane
Commits
-
Fix creation of resjunk tlist entries for inherited mixed UPDATE/DELETE.
- 39f180fdd1e6 9.5.11 landed
- 06ba5309682e 9.6.7 landed
- a57aa430b613 10.2 landed
- 9a785ad57317 11.0 landed