it happened again - wanted to get this post out before I do more  
digging:

table summary as an on delete cascade FK into sourcereports.
we delete from sourcereports.
the RI trigger deletes from summary (5700) but does not fire the log  
trigger yet.
we go on our merry way nuking events.
then my summary update trigger runs - the delete inside it does  
nothing due to the FK already nuking the row then proceeds to insert  
into it.
then we execute the slon logger for the original FK delete and it  
records a delete record after the insert.

then someone comes along and loads a new report for the same sourceid  
(to avoid confusion, it is a company identifier)

I need to flesh this out a bit more but I think it is related, I'll  
report back in a bit with more details.


--
Jeff Trout <jeff at jefftrout.com>
http://www.stuarthamm.net/
http://www.dellsmartexitin.com/