Wed Oct 5 14:59:10 PDT 2011
- Previous message: [Slony1-bugs] [Bug 239] Slony 1.2.22 and PG9.0 shows failure at failover
- Next message: [Slony1-bugs] [Bug 237] drop set does not remove truncate triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=243 Summary: Health Checks for foreign keys Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: core scripts AssignedTo: slony1-bugs at lists.slony.info ReportedBy: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 We should look for foreign key relationships that cross set boundaries from various perspectives: 1. Foreign key on replicated table pointing to a non-replicated table 2. Foreign key on non-replicated table pointing to a replicated table 3. Foreign key on replicated table pointing to a table in a different replication set with the same origin 4. Foreign key on replicated table pointing to a table in a different replication set with a different origin Other scenarios are uninteresting from a Slony perspective. There are several ways that these issues might be reported, and we may wish to consider using some or multiple of the following: a) Initial health check run by slon upon startup, calling stored function slon_node_health_check() b) The tool test_slony_state.pl c) Perhaps a stand-alone tool to add to tools -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 239] Slony 1.2.22 and PG9.0 shows failure at failover
- Next message: [Slony1-bugs] [Bug 237] drop set does not remove truncate triggers
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list