Tue Apr 26 08:31:45 PDT 2011
- Previous message: [Slony1-general] dropping trigger on slave
- Next message: [Slony1-general] pg_upgrade with Slony replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 26, 2011 at 11:07 AM, Steve Singer <ssinger at ca.afilias.info> wrote: > 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. Yep, "what Steve said." In version 2, it might become a reasonable proposition to drop the triggers directly, but on 1.2, Slony does way too much mucking around with the system catalog for it to seem remotely safe to do other than EXECUTE SCRIPT.
- Previous message: [Slony1-general] dropping trigger on slave
- Next message: [Slony1-general] pg_upgrade with Slony replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list