[...]
> Can you please run sqlite3_analyzer [...] on both
> the original database and the database after VACUUM
> and send me the output?
done, send 2 txt-files
greetings
Oliver
___
sqlite-users mailing list
sqlite-users@sqlite.org
* Oliver Schneider:
> just a few minutes ago I ran a VACUUM on a DB file and the size before
> was 2089610240 and afterwards 2135066624. Is this normal?
This is just typical behavior with B-trees because the fill factor
almost always changes when they are rebuilt. It seems that SQLite
doesn't
On Sat, Sep 18, 2010 at 11:36:12AM -0700, Kyle McKay scratched on the wall:
> On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote:
> > just a few minutes ago I ran a VACUUM on a DB file and the size before
> > was 2089610240 and afterwards 2135066624. Is this normal?
> Admittedly that's only
On Sat, Sep 18, 2010 at 2:36 PM, Kyle McKay wrote:
> On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote:
> > just a few minutes ago I ran a VACUUM on a DB file and the size before
> > was 2089610240 and afterwards 2135066624. Is this normal?
>
> I've recently been
On Sep 17, 2010, at 16:08:42 PDT, Oliver Schneider wrote:
> just a few minutes ago I ran a VACUUM on a DB file and the size before
> was 2089610240 and afterwards 2135066624. Is this normal?
I've recently been noticing the same thing, for example:
443182080 newdb.sq3
$ sqlite3 newdb.sq3
SQLite
> just a few minutes ago I ran a VACUUM on a DB file and the size before
> was 2089610240 and afterwards 2135066624. Is this normal?
>
>
If you have a copy of the old db and new db, can you check the results on
both databases of the following pragmas:
PRAGMA freelist_count;
PRAGMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there,
just a few minutes ago I ran a VACUUM on a DB file and the size before
was 2089610240 and afterwards 2135066624. Is this normal?
Thanks,
// Oliver
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
7 matches
Mail list logo