Geoffrey wrote:
Will it cause a problem if one adds fields to a table that is being
replicated?
That is, will it break the replication process, or will the
replication continue to simply replicate the previous set of fields?
There may be cases where replication won't break, but in general, if you
do not use the slonik "EXECUTE SCRIPT" facility to handle alterations of
the replicated schema, yes, indeed, you are likely to experience
problems that will notably include replication "falling over."
There is a trigger on each replicated table which needs to be aware of
what columns are in the table, and if you ALTER TABLE ADD COLUMN outside
of "EXECUTE SCRIPT," the trigger will therefore NOT be aware of the
change, which is likely to cause things to break down.
It is *possible* that repairs might be accomplished by dropping the
affected tables from replication (SET DROP TABLE), then creating a new
set, and setting up replication on them again. It is also entirely
likely that the best solution will be to re-initialize replication.
--
let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;;
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
