>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
