Fri May 27 13:34:48 PDT 2011
- Previous message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Next message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=217 --- Comment #2 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-05-27 13:34:48 PDT --- A solution strategy for this may be to create a function that rummages through all replicated tables, checking to see if the triggers have 'kvvkvk' values that correspond to the primary key for each respective table, fixing that, if it should fail to match. Such a function would be run by EXECUTE SCRIPT, automatically. It could presumably also be run manually, against each node, if someone has decided to mess with the tables by hand, via psql. -- 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 217] Changing the primary key of a replicated table leads to trouble
- Next message: [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list