> * What is the best practive for handling DDL changes to a database? Depends on what the change is. For small ones such as indexes, constraints, and column type changes, nothing needs to be done at all. For things like adding new columns, adding tables to a sync, and practically everything else, a restart of the sync is required (mostly because we cache all the column info at the start of the sync - while this could be done on the fly, the overhead is not worth it). The tricky cases come when you mess with the primary keys of replicated tables, in which case the best solution is to generally stop writing to the table, finish replicating, drop the old triggers, remove the table from Bucardo, re-add it to Bucardo, and run validate_sync.
-- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
pgpAIV8gw4wEx.pgp
Description: PGP signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
