Fri Sep 3 11:35:10 PDT 2010
- Previous message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: No subject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=128 --- Comment #9 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-09-03 11:35:10 PDT --- (In reply to comment #8) > 6) make sure that you do NOT run 'REPAIR CONFIG' because you've forgotten to > Thoughts? Step #6 is the "grand mistake" portion of this. The node's really rather broken because the tables aren't connected properly. Perhaps the solution is to make sure that the slon refuses to start if you forget to REPAIR CONFIG. One might do that by having slon do some "health checks" on the schema before it allows worker threads in to do work. If things are found "unhealthy," then the slon reports the problems, and terminates. The unhealthy state here would be that there is a disagreement between sl_table and the real set of tables in the database. -- 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.
- Previous message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: No subject
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list