Wed Jul 26 02:14:38 PDT 2006
- Previous message: [Slony1-general] EXECUTE SCRIPT with 1.1.5 - trying to do the Right Thing
- Next message: [Slony1-general] EXECUTE SCRIPT with 1.1.5 - trying to do the Right Thing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 26 Jul 2006 11:03:10 +0200 Csaba Nagy <nagy at ecircle-ag.com> wrote: > Well, if your script adds a column with default value to a huge table I > guess you wouldn't want a dry run first ;-) I certainly won't like slony > doing that by default. OK that's fair comment.. I guess DRYRUN=1 could be an option to the EXECUTE SCRIPT option though ;) > > That I don't understand, because I specified the script to run on set 2, but I am only seeing deadlocks on tables which are only in set 1! :( > > OK, then is it possible that your script affects those tables outside > the set ? It is possible for example if you modify foreign key relations > which point outside the set. That's why the slony docs state pretty > clearly you should stuff all tables related by FKs into the same set... I see. That's very likely to be the case, I'll look into that - thanks =) gdh
- Previous message: [Slony1-general] EXECUTE SCRIPT with 1.1.5 - trying to do the Right Thing
- Next message: [Slony1-general] EXECUTE SCRIPT with 1.1.5 - trying to do the Right Thing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list