hannu at skype.net wrote:
>>Hello,
>>
>>I've spent the last few days learning slony and setting it up on some
>>test databases with good results.  However, when I set up replication on
>>my live database, the slon processes startup and appear to be preparing
>>to copy things over when I get:
>>
>>"The postmaster has commanded this server process to roll back the
>>current transaction and exit, because another server process exited
>>abnormally and possibly corrupted shared memory."
>>
>>This happens continually until I uninstall the slony schema from my
>>database.
> 
> 
> Does slon  need to be running or is it happening even without it (maybe as
> a result of slony triggers doing something bad) ?

No, slon does not need to be running for the crashes to occur.

I'll work on getting a stack trace.

-Brad