Wed May 16 06:10:48 PDT 2012
- Previous message: [Slony1-bugs] [Bug 266] Slony-I: old key column tbl_stock_2012.comments IS NULL on UPDATE
- Next message: [Slony1-bugs] [Bug 266] Slony-I: old key column tbl_stock_2012.comments IS NULL on UPDATE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=266 --- Comment #1 from Steve Singer <ssinger at ca.afilias.info> 2012-05-16 06:10:48 PDT --- In Slony 1.2 and earlier most DDL changes need to be done via EXECUTE SCRIPT. You should not be adding columns to tables outside of EXECUTE SCRIPT. EXECUTE SCRIPT in 1.2 is a heavy locking operation. http://www.slony.info/documentation/1.2/ddlchanges.html Are the trigger arguments on the table corrupt/incorrect? The bug you link to talks about the attkind parameter. Running EXECUTE SCRIPT (this will lock all tables) will rebuild the attkind attributes. In some cases this might fix problems introduced by doing ALTER TABLE outside of an execute script. I consider Slony 1.2.x EOL I do not think we will be releasing any new versions or fixes for slony 1.2.x -- 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 266] Slony-I: old key column tbl_stock_2012.comments IS NULL on UPDATE
- Next message: [Slony1-bugs] [Bug 266] Slony-I: old key column tbl_stock_2012.comments IS NULL on UPDATE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list