[Bucardo-general] Replication aborted because of DDL change

[Greg Sabino Mullane]

> I got the following error message and the bucardo process got
> terminated. What happend was , a new column has been added to the
> master database and the same column has not been added to slave.
> Eventually, the replication was stopped with the following message.
> Do we have to stop the replication process , incase if there is a DDL
> change to master DB and make the same change to slave and resume the
> bucardo_ctl? Please help, kind of serious issue for us.

Yes. Postgres does not offer triggers on system tables, so there is 
no reliable way for Bucardo to detect such changes. The best way to 
make DDL changes is as you said: stop Bucardo, make the changes on both 
ends, then restart Bucardo.

There are long-term plans to automate some of that and have Bucardo 
automatically detect and apply things like new columns to the slaves, 
but it's still a very basic proof of concept at this point.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20100217/e987d809/attachment.bin