Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables
Date
Msg-id 18636.1511797772@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Bug in ExecModifyTable function and trigger issues forforeign tables  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: [HACKERS] Bug in ExecModifyTable function and trigger issues for foreign tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> I wonder if, years from now, it might look a bit odd that
> rewriteTargetListUD() is doing part of work of preptlist.c, is only
> called from there, and yet is located in the rewriter.

Yeah, I probably wouldn't have done it like this in a green field,
but maintaining traceability to the existing code is valuable IMO.

> A separate point -- it might be marginally more efficient to have the
> work of rewriteTargetListUD() done after expand_targetlist() to avoid
> the possible renumbering of the resjunk entries.

Hm.  It wouldn't save a lot, but yeah, doing it in this order seems
a bit silly when you put it like that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: [HACKERS] Refactoring identifier checks to consistently use strcmp
Next
From: Ildus Kurbangaliev
Date:
Subject: Re: [HACKERS] Custom compression methods