Hi. I currently have three nodes and two replication sets. Every month I need to alter the tables in the larger replication set while keeping the smaller replication set live. The scripts that do the alteration can take hours to run.
EXECUTE SCRIPT wants to lock all tables, despite me being a consenting adult who promises not to muck with tables outside of the specified SET ID set. Do I need to split things into two clusters? Are there other alternatives, such as a version of EXECUTE SCRIPT that has less paranoid locking behavior? I'm currently running 1.2.13 but can upgrade if needed. One option I could come up with with 2.0 would be drop the larger replication set entirely out of the cluster, run the scripts manually against each node, then rebuild the replication set using OMIT COPY but that just seems nasty - I'd probably be better off writing my own EXECUTE SCRIPT replacement that only locks and messes with the triggers of tables in the targeted set. -- Stuart Bishop <[email protected]> http://www.stuartbishop.net/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
