On Sun, Apr 14, 2013 at 11:46:07AM -0400, Jonathan Brinkman wrote: > [Sat Apr 13 18:54:04 2013] KID Warning! Aborting due to exception for > clientdata.security_clearanceevents_loops.loopeventid: 3505855 Error was > DBD::Pg::st execute failed: ERROR: could not serialize access due to > read/write dependencies among transactions\nDETAIL: Reason code: Canceled > on identification as a pivot, during write.\nHINT: The transaction might > succeed if retried. at /usr/local/share/perl/5.14.2/Bucardo.pm line 5815.
That's a normal serialization error. Can happen a lot on a busy system, as Bucardo needs to be at least read committed level. You might try cranking your default isolation_level down from serializable to 'read committed'. This is done at the sync level, or you can set it globally in the bucardo config: bucardo set isolation_level=read_committed If it still persists, the next step is to figure out why things are not serializing. On the bucardo side, you can try smaller tables-per-sync, and running the syncs more often. Otherwise, you have to look at what else is accessing the replicated tables and see if it can be more friendly (e.g. short transactions help). -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8
signature.asc
Description: Digital signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
