Andrew,

Thanks for the response!

Unfortunately, we don't have a core from the crash.  I ended up  
uninstalling slony because the crashes happened again. I also have  
since upgraded to 8.2.1.

The next time I use slony, i'll make sure I have everything compiled  
with debugging symbols and core files enabled so that I can provide  
better feedback if things take a turn for the worse.  Until then, I  
guess there's not much either of us can do to help each other out :)

I'm sure the correct libraries were linked against and that the same  
compiler was used.

Best Regards,

Brian Hirt

On Jan 30, 2007, at 6:09 AM, Andrew Sullivan wrote:

> On Mon, Jan 29, 2007 at 07:34:36PM -0700, Brian Hirt wrote:
>>
>> Is it possible that slony is causing these crashes?  I think that
>
> It is.  With a sig11, though, your best bet is to look at the core
> file that should be generated.  I assume you have compiled with
> debugging symbols, and that you don't have core file generation
> turned off.  If you can get a backtrace from that core file, it'd be
> handy.
>
> Are you sure, by the way, that Slony and Postgres were compiled by
> the same compiler, and that Slony was compiled against the right
> libraries?  It's possible to introduce a subtle incompatibility that
> way.
>
>> NOTICE:  Slony-I: cleanup stale sl_nodelock entry for pid=8572
>> CONTEXT:  SQL statement "SELECT  "_mobycluster".cleanupNodelock()"
>>          PL/pgSQL function "cleanupevent" line 77 at perform
>>
>> Are they something to be worried about?
>
> No.
>
> A
>
> -- 
> Andrew Sullivan  | ajs at crankycanuck.ca
> Unfortunately reformatting the Internet is a little more painful
> than reformatting your hard drive when it gets out of whack.
> 		--Scott Morris
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general