If its an enhancement, in the meantime should the documentation for page size be fixed?
"If the SQLITE_ENABLE_ATOMIC_WRITE option is disabled or if xDeviceCharacteristics reports no suitable atomic write page sizes, then the default page size is the larger of SQLITE_DEFAULT_PAGE_SIZE and 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 <nlovell at tivo.com> 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 characteristic of >> SQLITE_IOCAP_POWERSAFE_OVERWRITE > OK. We have your enhancement request. > > >> (which is ironic since the device is >> power safe overwrite, but only if its the erase block size). >> This ends up meaning that the page_size always returns >> SQLITE_DEFAULT_PAGE_SIZE regardless of sector size. >> >> Obviously I could get around this by running pragma page_size prior to >> making the database in the first place, but that seems unnecessary >> considering that I already have a VFS layer in place. >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users at mailinglists.sqlite.org >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >> >
