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

From: rmd22 <rohit(dot)dhamane(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date: 2010-11-17 17:17:39
Message-ID: 1290014259723-3269442.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Fetter 2010-11-17 17:24:26 Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Previous Message David W Noon 2010-11-17 16:56:44 Re: Read binary records