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

Поиск
Список
Период
Сортировка
От David Fetter
Тема Re: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Дата
Msg-id 20101117172426.GG22765@fetter.org
обсуждение исходный текст
Ответ на Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE  (rmd22 <rohit.dhamane@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: rmd22
Дата:
Сообщение: Re: Storing old and new tuple values after an UPDATE, INSERT or DELETE
Следующее
От: Richard Broersma
Дата:
Сообщение: Re: Alter table to "on update cascade"