On Thu, Dec 8, 2011 at 3:19 PM, Jesus Garcia <jeg...@gmail.com> wrote:
> > 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?. Yes, but it doesn't matter. The last page written is the page that marks the transaction as committed. Until that is written, the updates made by the transaction will be removed when the record is revisited after the server restarts. > 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.' Sorry, the last time I had any influence on InterBase was late July 2000. I can say for sure that Firebird has fixed a number of problems, including a recent change that makes forced writes actually work for Linux. > > 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. Perhaps others on the list will describe their experiences. Architecturally, it should work, but the difference between architecture and implementation is bugs. And bugs happen. Firebird has the advantage of having thousands of eyes (well, scores at least) on the code. Good luck, Ann ------------------------------------------------------------------------------ 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
