> 03.04.2012 10:44, Vlad Khorsun wrote:
>> To not read whole database searching
>> for the not encrypted pages after restart i offer to store last encrypted
>> page number
>> at header page (also, obviously, we need to store encription state on the
>> header
>> such as "clear", "encrypted", "encryption is in progress", "decryption is in
>> progress").
>
> Do you suggest to write header page after writing of every single encrypted
> page, thus
> doubling I/O?..
We can
a) don't write header page immediately to disk after change encrypted page
number
b) change encrypted page number every N pages, where N >> 1
Regards,
Vlad
PS Of course, change of encryption state should be written to disk immediately
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
