I never said it would cover all possibilities. I just said that instead of "guessing" or stay only with the "theory", a real test could give more trustful results ;)
Carlos Firebird Performance in Detail - http://videos.firebirddevelopersday.com www.firebirdnews.org - www.FireBase.com.br EHehdfs> Am 19.08.2014 um 18:30 schrieb 'Carlos H. Cantu' [email protected] EHehdfs> [firebird-support]: >> Re: [firebird-support] Forced write, page size and buffer size The >> best thing would be if someone could simulate some crashes (like power >> failure) in both configurations and report back about existence of >> corruption. EHehdfs> Such an simulation does hardly cover all possible problems. EHehdfs> In general there was an statement about old interbase database which EHehdfs> should be "up again" shortly after an power fail in an tank-environment EHehdfs> caused by firing the gun. There is some chance that firebird can recover EHehdfs> after crash. EHehdfs> The Problem itself does arise from the order the physical writes are EHehdfs> done. If the OS (or even the disk) does reorder writes I would suspect EHehdfs> to generate problems. EHehdfs> You can simulate power-fail by using QEMU emulation and killing the EHehdfs> emulator. EHehdfs> Elmar EHehdfs> ------------------------------------ EHehdfs> ------------------------------------ EHehdfs> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ EHehdfs> Visit http://www.firebirdsql.org and click the Documentation item EHehdfs> on the main (top) menu. Try FAQ and other links from the left-side menu there. EHehdfs> Also search the knowledgebases at EHehdfs> http://www.ibphoenix.com/resources/documents/ EHehdfs> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ EHehdfs> ------------------------------------ EHehdfs> Yahoo Groups Links
