I have a PLpgSQL AFTER UPDATE constraint trigger that calls a trigger function with an embedded select statement.
The select statement queries the affected table and returns a mult-result set that includes the record equivalent to NEW. However, It seems the select doesn't yet see the non-committed records. I.E. the record that should be equal to NEW is in fact equal to OLD. Is this correct? Is there a way to adjust the visibility so that yet-to-be committed tuples are seen by the trigger function? Regards, Richard Broersma Jr. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
