Achilleus Mantzios wrote: > O Tom Lane έγραψε στις Feb 24, 2006 : > > > By definition, an AFTER trigger is too late to change what was > > stored. Use a BEFORE trigger. > > Too late if someone wants to store it. > I wanna store the intented original values, thats why i use > AFTER trigger. > But i would like to alter what a final AFTER trigger would see. > > I'll elabarote a little. > > An update happens. > The row is stored. > An after trigger is fired that alters some NEW columns > (nullifies them), aiming for a subsequent trigger > to see the altered results . > > It should be something like a pointer to a HeapTuple, (right?), > so that would be feasible i suppose. > > I would not even make a post if it was something that trivial. > > I hope you get my point.
Your real problem is that the "subsequent" trigger has behaviour you don't like. That's what you should be fixing. If dbmirror has no way to exclude specific tables from mirroring, take it up with them as a feature request, or patch dbmirror to work how you want it to. AFTER triggers *must* receive the row that was actually inserted/updated/deleted. If they could receive a "modified" row that didn't reflect what was actually in the database, all sorts of useful trigger-based logging and replication patterns wouldn't work, and there's really no other way to implement them. See also Tom Lane's other message for further implications of being able to modify the rows seen by AFTER triggers. I'd also be hesitant to write triggers that have to execute in a specific order. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
