Hi,

I encountered some duplicate key errors in my slony cluster today.  Clearly, 
an event/log was replicated more than once.

I believe that this may be due to "the Solaris threading issue", but I can't 
find enough clear information about this problem to determine whether I 
failed to avoid it in the build of Postgresql and Slony.

Detais:
 Solaris 9 sparc, 7.3.13, compiled with --thread-safety 
 Solaris 10 opteron, 8.0.6, compiled with --thread-safety
 All the slon's were running from the 8.0.6 instance/build.

I was able to manually remove the offending rows and get the slon's processing 
events again, but I'm worried about a few things:

1. How is my data?  Do I need to re-sync?
2. How can I prove that this problem is related to threading issue?
3. What IS the threading issue?  I can't find a good description of the
    problem and the solution.
4. If the problem still exists on the 8.0.X build, how do I correct it?

Any input and assistance would be appreciated.

-Michael