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

From: David Fetter <david(at)fetter(dot)org>
To: rmd22 <rohit(dot)dhamane(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Date: 2010-11-17 17:24:26
Message-ID: 20101117172426.GG22765@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Broersma 2010-11-17 17:42:55 Re: Alter table to "on update cascade"
Previous Message rmd22 2010-11-17 17:17:39 Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE