If I'm reading the logs right, this was routed through a Slonik Execute
Script command. Would it have called ddlScript_prepare otherwise?

 

From: Melvin Davidson [mailto:melvin6925 at yahoo.com] 
Sent: Wednesday, March 24, 2010 3:51 PM
To: slony1-general at lists.slony.info; Michael Holt
Subject: Re: [Slony1-general] deadlock from slony cleanup

 

>So it looks to me like the issue was caused by a ddl script running at
the same time as a >slony cleanupEvent command. Our system requires some
dynamic changes to our db >structure (in the form of new partitions and
things like that) these ddl scripts could run at >any time. So, how can
I best manage this around the cleanupEvents?


I would suggest you route all DDL changes through a SLONIK EXECUTE
SCRIPT. That also insures all DDL is propagated to all slaves.

Melvin Davidson 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100325/6b39ee66/attachment.htm