2011/12/8 Ann Harrison <aharri...@nuodb.com>
>
> An abnormal shutdown for any cause - power failure, O/S crash,
> Firebird crash will not corrupt the database if you have forced writes
> turned on and if your disk system actually forces writes in the order
> they are presented. Connections are transient, in memory entities and
> they go away. Active transactions remain in the active state on disk
> and are marked as rolled back when the database restarts. Their
> changes are undone as they are discovered.
If using superserver, when the abnormally shutdown starts, if another
thread is committing and updating a big amount of pages of several types,
the commit process can be terminated without finish, and some pages are
writen and another not. Could this happen?.
I ask it because i have had corruptions with interbase 2007 and 2009 when
the engine termitnate abnormally, some of them heavy, with forced writes. I
know IB is not FB, but IB people also say that with forced writes there is
no corruption, but is not true.
By the moment Firebird 2.5.1 is quite stable and the engine is working for
months without problems, but i would like to know it to feel better.
Jesus
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
