SPI_modifytuple - why i cant use it in trigers fired after

Поиск
Список
Период
Сортировка
Искать
От
Marek Bartnikowski
Тема
SPI_modifytuple - why i cant use it in trigers fired after
Дата
Msg-id
Pine.LNX.4.21.0110221041190.2226-100000@easy
Ответ на
Bug #488: Apache daemon dying on segfault from postgres (pgsql-bugs@postgresql.org)
Список
Дерево обсуждения
Bug #488: Apache daemon dying on segfault from postgres pgsql-bugs@postgresql.org
Re: Bug #488: Apache daemon dying on segfault from postgres Tom Lane <tgl@sss.pgh.pa.us>
SPI_modifytuple - why i cant use it in trigers fired after Marek Bartnikowski <marek@virt.pl> 
fragment from PostgreSQL 7.1 Documentation:
"Trigger functions return HeapTuple to the calling Executor. This is
ignored for triggers fired after an INSERT, DELETE or UPDATE operation but
it allows BEFORE triggers to: ......"

can somebody tell my why ? is it bug or what ?
sometimes i have to use it AFTER insert, update or delete. what can i do
in this situation.

thank you in advance


--
Marek Bartnikowski 
PostgreSQL DBA
C, PHP Prog.
В списке pgsql-bugs по дате отправления
Предыдущее
От: pgsql-bugs@postgresql.org
Дата:
Следующее
От: Tom Lane
Дата:
FAQ