Bug 19 - fresh schema for a logshipped node - keeping triggers out
Summary: fresh schema for a logshipped node - keeping triggers out
Alias: None
Product: Slony-I
Classification: Unclassified
Component: other scripts (show other bugs)
Version: devel
Hardware: All All
: medium normal
Assignee: Slony Bugs List
URL: http://lists.slony.info/pipermail/slo...
Depends on:
Reported: 2007-11-29 13:50 UTC by Christopher Browne
Modified: 2007-12-03 08:30 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Browne 2007-11-29 13:50:49 UTC
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
Comment 1 Christopher Browne 2007-11-29 13:52:29 UTC
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.
Comment 2 Christopher Browne 2007-12-03 08:30:21 UTC
Committed a new tool to search the source schema for triggers/rules.