On Fri, Jan 16, 2009 at 2:45 AM, Alan Hodgson <[email protected]> wrote:
>
> > I have a single master / single slave set up with Slony-I 1.2.11 and PG
> > 8.2. It has been running well for quite a long time until yesterday, when
> > after executing a DDL script on the master server, the replication broke.
> > The DDL script just added a column to a table in the replication set.
>
> 1.2.11 had a bug that could cause this in the event of a temporary problem
> applying DDL scripts. Fortunately it was fixed in 1.2.12, which was
> released well over a year ago.
>
> Unfortunately, your replication is almost certainly hosed. But if you
> upgrade Slony and resubscribe your slave(s), you won't experience the same
> problem again.
>
Thanks Alan.
By 'hosed' I take it that you mean the replication is broken beyond repair
(sorry I am no native English speaker)? To be sure, is the following the
correct way to proceed:
1. On the master node, run slonik with:
unsubscribe set (id=1, receiver=2)
2. Stop slon on both master and slave and upgrade slony version and start
slon on both nodes
3. On the master node, run slonik with:
subscribe set(id=1, provider=1, receiver=2, forward=yes)
Is that all and I don't need to touch the tables that were replicated and
are now out of sync on the slave?
--
Hong Yuan
大管家网上建材超市
装修装潢建材一站式购物
http://www.homemaster.cn
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
