When getting sqlite_corrupt when reading from a database, is there a way to
know if a particular failure came from reading/initializing a page from a WAL
file, or the database disk file?
Specifically I've been seeing a number of failures around btreeInitPage.
However when I pull up the saved c
quent and automatically "recovered" from).
From: sqlite-users on behalf of
Simon Slavin
Sent: Monday, November 6, 2017 3:53:41 PM
To: SQLite mailing list
Subject: Re: [sqlite] Tracking database corruption
On 6 Nov 2017, at 10:38pm, Nicholas Lovell wrote:
this,
but none of which are relevant for this).
From: sqlite-users on behalf of
Simon Slavin
Sent: Tuesday, November 7, 2017 8:43 AM
To: SQLite mailing list
Subject: Re: [sqlite] Tracking database corruption
On 7 Nov 2017, at 1:11am, Nicholas Lovell wrote:
I have my own VFS layer, and recently started trying to get the default
page size to actually match the real device erase block size depending
on the actual device the database is running on.
What I've found is that the xSectorSize method in the VFS is *not*
called unless I unset the device cha
d the
sector size as reported by the xSectorSize method of the
sqlite3_io_methods <https://www.sqlite.org/c3ref/io_methods.html>
object, but not more than SQLITE_MAX_DEFAULT_PAGE_SIZE"
(https://www.sqlite.org/pragma.html#pragma_page_size)
> On 4/6/15, Nicholas Lovell wrote:
>>
5 matches
Mail list logo
