08.08.2011 22:14, Kjell Rilbe wrote: > Any indication of how large the lag (N) could be? Can it grow without > bounds if the server load is high?
I can say for sure only for replicator by IBPhoenix: It depends on replication settings and timing. If crash occur after replication finish but before commit of the next transaction, N=0. If replication is event-driven and crash occur during replication, N=1. If replication is scheduled, N <= tpm / replication frequency. If server load overflow replicator's throughput, N can grow to the sky. Here when I say "crash" I mean complete and unrecoverable destruction of source database. For other replicators numbers may differ. -- SY, SD. ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
