SPI_modifytuple - why i cant use it in trigers fired after - Mailing list pgsql-bugs

From Marek Bartnikowski
Subject SPI_modifytuple - why i cant use it in trigers fired after
Date
Msg-id Pine.LNX.4.21.0110221041190.2226-100000@easy
Whole thread Raw
In response to Bug #488: Apache daemon dying on segfault from postgres  (pgsql-bugs@postgresql.org)
List pgsql-bugs
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 <mailto:marek@virt.pl>
PostgreSQL DBA
C, PHP Prog.

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #489: pg_dump places GRANT queries before CREATE VIEW
Next
From: Tom Lane
Date:
Subject: Re: Bug #489: pg_dump places GRANT queries before CREATE VIEW