I have similar problem some time ago, and my whole base stayed innoperated.
Too bad.
Vacuum isn't good when Slony is initing for the first time (create set,
subscribe set and so on).
The only solution that I find is to do the sets slowly, one by one. Then the
Slony does the work great.

Regards,

Rafael Domiciano

2008/7/25 Gurjeet Singh <singh.gurjeet at gmail.com>

> Hi All,
>
>     The docs for CREATE SET say 'No application-visible locking should ta=
ke
> place'. But we saw that it was hung, and noticed that there was a VACUUM
> running on master node. We waited for quite a while, and after we killed
> that VACUUM, the CREATE SET moved forward.
>
>     PG is 8.1.11, and Slony is 1.2.14, if that helps.
>
> Best regards,
> --
> gurjeet[.singh]@EnterpriseDB.com
> singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
>
> EnterpriseDB http://www.enterprisedb.com
>
> Mail sent from my BlackLaptop device
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-hackers/attachments/20080725/=
a51e7a18/attachment-0001.htm