Mon Mar 19 22:42:50 PDT 2007
- Previous message: [Slony1-general] Execute script and "execute only on"
- Next message: [Slony1-general] Execute script and "execute only on"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ssinger_pg at sympatico.ca wrote: > > Once you start performing execute scripts only on some nodes then your > data and/or schema won't be the same everywhere in the cluster and in > any master/slave replication system if you don't do this very > carefully your going to get burned. > > Maybe we should start with trying to decide what the purpose of > execute script is. My original purpose why I used EXECUTE ONLY ON was similar to this case by Jeff Frost: http://lists.slony.info/pipermail/slony1-general/2006-November/005216.html To summarize, I had a non-replicated table which had a foreign key to a replicated table on a subscriber node. When trying to drop the non-replicated table, I run into problems with Slony's "catalogue fiddling", and EXECUTE ONLY ON was the only (reasonable) way to fix things. Fortunately I had up-to-date backups when I discovered that the table was dropped at both nodes.. :) Regards, MP
- Previous message: [Slony1-general] Execute script and "execute only on"
- Next message: [Slony1-general] Execute script and "execute only on"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list