Bucardo 4.5.0 Yes there are some triggers set to ALWAYS ALTER TABLE clientdata.persons_accessids_idsystem_images ENABLE TRIGGER bucardo_add_delta; ALTER TABLE clientdata.persons_accessids_idsystem_images ENABLE TRIGGER bucardo_triggerkick_cmsorca_swap_main_and_gate; ALTER TABLE replication.replication_club_persons ENABLE TRIGGER trcrossschema_updater_clubpersons; ALTER TABLE replication.replication_club_persons ENABLE TRIGGER bucardo_add_delta; ALTER TABLE replication.replication_club_persons ENABLE TRIGGER bucardo_triggerkick_cmsorca_pushdelta_main_to_gate;
That was done because the tables are "double-hopping", in that when the slave db updates the cloud db, there is an AFTER trigger that runs on the cloud DB table that needs to ALWAYS fire so that other stuff happens. Maybe I'm doing that wrong? -----Original Message----- From: Greg Sabino Mullane [mailto:[email protected]] Sent: Friday, July 25, 2014 11:42 PM To: Jonathan Brinkman Cc: [email protected] Subject: Re: [Bucardo-general] trigger-war? On Thu, Jul 24, 2014 at 04:58:37PM -0400, Jonathan Brinkman wrote: > Running Bucardo4 on ubuntu 12.04LTS and Postgresql 9.3 What exact version of Bucardo? There was a similar issue with Bucardo 5 that was fixed not too long ago, but I don't think it affected Bucardo 4. Are the sync kick triggers on the tables set as "ALWAYS" perchance? -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 _______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
