Tom Lane d2e17e1ddc Fix mishandling of after-trigger state when a SQL function returns multiple
rows --- if the surrounding query queued any trigger events between the rows,
the events would be fired at the wrong time, leading to bizarre behavior.
Per report from Merlin Moncure.

This is a simple patch that should solve the problem fully in the back
branches, but in HEAD we also need to consider the possibility of queries
with RETURNING clauses.  Will look into a fix for that separately.
2006-10-12 17:02:24 +00:00
..
2006-10-10 21:31:44 +00:00
2006-10-04 00:30:14 +00:00
2006-10-04 00:30:14 +00:00
2006-10-10 00:30:32 +00:00
2006-09-27 16:19:42 +00:00
2006-07-10 15:50:02 +00:00
2006-08-08 22:44:05 +00:00