Wait, does https://www.sqlite.org/fileformat2.html say that database pages
have an index number stored (so if storage messes up sequence of sectors,
will SQLite notice)?


Right, exactly http://www.sqlite.org/src/tktview?name=72b01a982a .

And that means the underlying FS needs to make the checksumming, for there
to be any "more real" integrity guarantees.

What relevance do you guys see in introducing this?



(* A underlying FS can make additional integrity by using checksums *and*
mirrors, however, SQLite introducing a checksum-based integrity guarantee
model is like Very valuable so really having both is only good :) )


2015-07-14 15:59 GMT+02:00 Simon Slavin <slavins at bigfraud.org>:

>
> On 14 Jul 2015, at 2:53pm, Mikael <mikael.trash at gmail.com> wrote:
>
> > This is awesome as it's a quite nice data integrity guarantee: this
> > guarantees that data is in the right place (so broken sector mapping
> tables
> > won't break anything) and is correct!
> >
> > Does SQLite do the same, what about SQLite do the same, patch?
>
> For details on the SQLite file format see
>
> <https://www.sqlite.org/fileformat.html>
> <https://www.sqlite.org/fileformat2.html>
>
> As you can see, journal pages carry checksums, database pages don't.
>
> Simon.
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>

2015-07-14 17:25 GMT+02:00 Roger Binns <rogerb at rogerbinns.com>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/14/2015 06:53 AM, Mikael wrote:
> > Does SQLite do the same, what about SQLite do the same, patch?
>
> The SQLite authors rejected checksumming SQLite database pages.  The
> existing integrity check will only catch issues that happen in
> sufficiently important metadata, but in general won't catch corruption.
>
>   http://www.sqlite.org/src/tktview?name=72b01a982a
>
> Roger
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iEYEARECAAYFAlWlKfgACgkQmOOfHg372QTW0gCgn5PVs7z9G6FEu5dG31hbRNy1
> jAIAniXv0ebDjsCuroOrkwI7D4Wszwno
> =sV74
> -----END PGP SIGNATURE-----
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

Reply via email to