On Sun, May 14, 2017 at 9:54 PM, Dilip Kumar <dilipbal...@gmail.com> wrote: > After your fix, now tupleid is invalid which is expected, but seems > like we need to do something more. As per the comments seems like it > is expected to get the oldtuple from planSlot. But I don't see any > code for handling that part.
Maybe we should do something like attached patch. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
fix_fdw_trigger.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
