19 2007-11-29 13:50:00 -0800 fresh schema for a logshipped node - keeping triggers out 2007-12-03 08:30:21 -0800 1 1 1 Unclassified Slony-I other scripts devel All All RESOLVED FIXED http://lists.slony.info/pipermail/slony1-general/2007-October/006763.html medium normal --- 1 cbbrowne slony1-bugs jpfletch slony1-bugs cbbrowne 2007-11-29 13:50:49 -0800 How is it that i'm supposed to get clean schema for a logshipped node? I've previously pg_dumped form the log shipped node's provider, which is itself a subscriber. On some dbs, however, i've run into the 'pg_dump sanity check failed' issue when dumping from a subscriber, so I though i'd try slony1_extract_schema.sh. This extracts schema fine from an origin, but won't work for a log shipped node (i.e the output of slony1_dump.sh won't apply) unless I manually drop all of the triggers and constraints that are present on the origin... -- JP Fletcher, Afilias Canada cbbrowne 2007-11-29 13:52:29 -0800 Intention: To provide a script that may be run against a fresh log shipping node (e.g. - with schema) to search out triggers on replicated tables and suggest that the Gentle User consider dropping them. cbbrowne 2007-12-03 08:30:21 -0800 Committed a new tool to search the source schema for triggers/rules. http://lists.slony.info/pipermail/slony1-commit/2007-December/002102.html http://lists.slony.info/pipermail/slony1-commit/2007-December/002101.html