>> So, before CORE-2648 was fixed, delta file was always opened in FW=OFF
>> mode
>> despite of database settings.
>
> So, if the server crashes, we have a problem here?
If database setting is FW = ON but (before the fix) delta file is opens
with FW = OFF
then Firebird crash in stalled (or merge) mode could corrupt delta file
contents. Note, it
*could be* corrupted but it is not necessary since OS still have dirty pages in
its file cache
and will write it on disk sooner or later.
But if OS is crashed then corruption is very possible.
> Or does writing the
> delta file also take both config options mentioned above into account?
Of course.
>> Before CORE-3521 was fixed delta file contents was not
>> flushed to disk when transactions finished.
>
> So, without a fix for CORE-3521, cached dirty pages aren't written to
> disk while nbackup is running at all?
If FW = ON, then this bug should have no impact. If FW=OFF then *on disk*
contents of delta
file fully depends on OS and its policy of delayed writes. I.e. it is OS
decides when to write dirty
pages on disk. Since bug is fixed we have equal safety in any nbackup mode.
> Do both issues relate to corrupting the database in any way?
Probably.
Regards,
Vlad
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
