Tue Apr 26 08:07:24 PDT 2011
- Previous message: [Slony1-general] dropping trigger on slave
- Next message: [Slony1-general] dropping trigger on slave
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11-04-26 10:59 AM, Frank McGeough wrote: > > Steve, > > The drop table on table "B" worked fine. The problem that I have is that the trigger is on table "A" - which is still replicated. > > To state the question as generally as I can : how do you drop triggers within a Slony replicated system? There are always cases where you realize a trigger on a replicated table is no longer needed. What do you do in that case? What is the Slony prescribed procedure for dealing with that? To drop a non-slony installed trigger on a replicated table in 1.2 you use EXECUTE SCRIPT. When the EXECUTE SCRIPT command/event runs on the slave it will restore all replicated tables to the unaltered state for the duration of the script. Keep in mind that EXECUTE SCRIPT in 1.2 is a heavy locking operation. > > > Thanks, > Frank > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general
- Previous message: [Slony1-general] dropping trigger on slave
- Next message: [Slony1-general] dropping trigger on slave
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list