Subject Re: [firebird-support] FW and Journaling
Author Carlos H. Cantu
Re: [firebird-support] FW and Journaling

As long as the transaction is committed, the data is replicated. That's better than forced writes on.

Ok, you didn't provide enough information on how your replication works, so it is hard to think about all the possibilities :) Even with synchronous replication, commiting doesnt mean that the data was really saved in the disk, so if your replication is made by a third part software (not by triggers and execute statement), I think there is still a chance of commited work not being replicated in the case of DB getting corrupted before the replication happens.

Anyway, this already is going far from the original question ;-)

Firebird Performance in Detail - -

On 29/09/2013 11:40 PM, "Carlos H. Cantu" <listas@...> wrote:
AM> I would use neither. But I'm a replicator by nature. Another cheap box just
AM> next to the production box and you get high performance and also safety and
AM> the ability to hotswap.
AM> Alan

Thanks for your opinion, but replication is not in question in this
case. Also, if data fails to be saved in your production database, it
will not be replicated.

Firebird Performance in Detail - -

>> Question is:
>> What would be safer:
>> Keep FW OFF and Journaling ON
>> or
>> Keep FW ON and Journaling OFF
>> ?