Fri Apr 7 11:24:03 PDT 2006
- Previous message: [Slony1-general] is there a way to delete a schema change sync event?
- Next message: [Slony1-general] Scheduled downtime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Miguel wrote: > Me too :-), sounds easier. > Ok, the replication started again after i created the user in slave, > im guessing that the rule "dont make schema changes in a live > cluster , use excecute scrips instead" dont apply to all objects... If a change to, say, a stored procedure needs to be applied on all nodes at the same point in the transaction stream, then EXECUTE SCRIPT is the way to go. But I don't imagine that's usually the case, and for changes like that, it may actually be safer to apply such changes by running a script that connects to each node, and not get Slony-I involved. Basically, the things you *MUST* apply via EXECUTE SCRIPT are any changes that directly affect replicated tables or sequences. - You're altering a non-replicated table? No value to using EXECUTE SCRIPT. - You're adding a new stored function? No value to using EXECUTE SCRIPT. - You're replacing a view? No value to using EXECUTE SCRIPT.
- Previous message: [Slony1-general] is there a way to delete a schema change sync event?
- Next message: [Slony1-general] Scheduled downtime
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list