Tue Aug 31 08:56:06 PDT 2010
- Previous message: [Slony1-bugs] [Bug 40] libpq thread test insufficient
- Next message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=128 --- Comment #4 from Steve Singer <ssinger at ca.afilias.info> 2010-08-31 08:56:06 PDT --- I'm not sure this fixes the bug described here. Recall the sequence of events described here is 1. User does a "DROP TABLE someReplicatedTable" (Say he does this on all nodes) 2. The user does a MOVE SET via slonik The move set will fail on the subscriber in alterTableConfigureTriggers the subscriber will be stuck on the move set and won't be able to get to a 'set drop table' command that your patch changes. I think alterTableConfigureTriggers() also needs the check against pg_class and to log a warning if it isn't found. Right not it throws a fatal exception. -- 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 40] libpq thread test insufficient
- Next message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list