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

From David Fetter
Subject Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date
Msg-id 20101117172426.GG22765@fetter.org
Whole thread Raw
In response to Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (rmd22 <rohit.dhamane@gmail.com>)
List pgsql-general
On Wed, Nov 17, 2010 at 09:17:39AM -0800, rmd22 wrote:
>
> 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?

Yes, but it's insanely risky, and an enormous amount of work that by
asking that question you're showing you're not qualified to do.

> And also what about fast path interface?  Is it possible to use it
> instead?

Before you go anywhere like this, do some testing on things that work
for the vast majority of people. :)

Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

pgsql-general by date:

Previous
From: rmd22
Date:
Subject: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Next
From: Richard Broersma
Date:
Subject: Re: Alter table to "on update cascade"