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:[email protected]] Sent: Wednesday, March 24, 2010 3:51 PM To: [email protected]; 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
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
