On 2 Aug 2019, at 8:55pm, Jen Pollock wrote:
> Compressing the backups would likely save you a lot more space, and I
> suspect it wouldn't be affected that much by page size; presumably empty
> space at the ends of pages will compress very well.
It might be an interesting exersize to compare th
thought I'd ask.
>
> -Original Message- From: David Raymond
> Sent: Wednesday, July 31, 2019 10:48 PM
> To: SQLite mailing list
> Subject: Re: [sqlite] Quick way to determine optimal page size?
>
> Not that I'm aware of no. How much of a difference are you
From: David Raymond
Sent: Wednesday, July 31, 2019 10:48 PM
To: SQLite mailing list
Subject: Re: [sqlite] Quick way to determine optimal page size?
Not that I'm aware of no. How much of a difference are you seeing for your
database size depending on the page size you try?
-Original M
On 31 Jul 2019, at 8:28pm, Tony Papadimitriou wrote:
> Instead of brute force “pragma page_size=xxx; vacuum;” for each page size and
> each database to determine which one produces the smallest file, is there
> some quicker way?
It might be faster to
make a new file,
set page size,
ATTACH the
bject: [sqlite] Quick way to determine optimal page size?
Instead of brute force “pragma page_size=xxx; vacuum;” for each page size and
each database to determine which one produces the smallest file, is there some
quicker way?
Thanks.
___
sqlite-
Instead of brute force “pragma page_size=xxx; vacuum;” for each page size and
each database to determine which one produces the smallest file, is there some
quicker way?
Thanks.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://
6 matches
Mail list logo
