Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE

Yes it's the "performance issue".
I am going to talk to them about the triggers tomorrow.
On the other hand I would still like to know if it is possible to do it by
modifying the execMain.c or nodeModifyTable.c files?
And also what about fast path interface? Is it possible to use it instead?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Storing-old-and-new-tuple-values-after-an-UPDATE-INSERT-or-DELETE-tp3269108p3269442.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.