Postgres Pro
Downloads
Home   >   mailing lists

Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE - Mailing list pgsql-general

From rmd22
Subject Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date
Msg-id 1290014259723-3269442.post@n5.nabble.com
Whole thread Raw
In response to Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (David Fetter <david@fetter.org>)
Responses Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (David Fetter <david@fetter.org>)
List pgsql-general
Tree view 
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.

pgsql-general by date:

Previous
From: David W Noon
Date:
Subject: Re: Read binary records
Next
From: David Fetter
Date:
Subject: Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE