On 3/7/17, Olivier Mascia wrote:
>> Le 7 mars 2017 à 04:13, Richard Hipp a écrit :
>>
>> the database connection remembers (in RAM) specifically which
>> tables and indexes it has considered for use and will only run ANALYZE
>> on those tables for which some
> Le 7 mars 2017 à 04:13, Richard Hipp a écrit :
>
> the database connection remembers (in RAM) specifically which
> tables and indexes it has considered for use and will only run ANALYZE
> on those tables for which some prior query would have benefited from
> having good
On Mon, 6 Mar 2017 18:52:48 -0500
Richard Hipp wrote:
> On 3/6/17, Simon Slavin wrote:
> >
> >> See
> >> https://www.sqlite.org/draft/pragma.html#pragma_optimize for
> >> additional information.
> >
> > I?m sure this is extremely far-future-looking, but a
Very interesting development, thanks for pushing the boundaries at each new
release!
Would it be possible to consider some form of deferred optimize?
ie. rather than optimize when closing the connection, it would just write
the optimize info gathered during the heavy queries, for use in a future
Richard Hipp wrote...
On 3/6/17, jose isaias cabrera wrote:
Richard Hipp wrote...
Have you ever wondered when you should run ANALYZE on an SQLite
database? It is tricky to figure out when that is appropriate. The
Thanks for this. I actually run this ANALYZE
On 3/6/17, jose isaias cabrera wrote:
>
> Richard Hipp wrote...
>
>>Have you ever wondered when you should run ANALYZE on an SQLite
>>database? It is tricky to figure out when that is appropriate. The
> Thanks for this. I actually run this ANALYZE weekly with a script.
Richard Hipp wrote...
Have you ever wondered when you should run ANALYZE on an SQLite
database? It is tricky to figure out when that is appropriate. The
Thanks for this. I actually run this ANALYZE weekly with a script. This
will be better. I can run it everyday don't do any harm.
On 3/6/17, Simon Slavin wrote:
>
>> See
>> https://www.sqlite.org/draft/pragma.html#pragma_optimize for
>> additional information.
>
> I’m sure this is extremely far-future-looking, but a default mask of 254
> (0xfe) might be better than the stated default of 14 (0x0e).
On 6 Mar 2017, at 9:30pm, Richard Hipp wrote:
> See
> https://www.sqlite.org/draft/pragma.html#pragma_optimize for
> additional information.
I’m sure this is extremely far-future-looking, but a default mask of 254 (0xfe)
might be better than the stated default of 14 (0x0e).
> On Mar 6, 2017, at 1:30 PM, Richard Hipp wrote:
>
> Have you ever wondered when you should run ANALYZE on an SQLite
> database? It is tricky to figure out when that is appropriate. The
> new "PRAGMA optimize" command tries to automate the decision for you.
Very nice!!
There is a fresh source-code snapshot of the unreleased 3.18.0 version
of SQLite up on the download page:
https://www.sqlite.org/download.html
https://www.sqlite.org/draft/releaselog/3_18_0.html <--- Change log
Have you ever wondered when you should run ANALYZE on an SQLite
database?
11 matches
Mail list logo