On 28/12/2012 4:04 PM, Krzysztof wrote:
I don't understand :/ So what is solution in my case?
What is the problem you need to solve? If I understand correctly, your
app repeatedly creates and deletes ~80MB of temp data. If so, it's
actually a good thing that sqlite doesn't release the memory,
On Sat, 29 Dec 2012 00:04:12 +0100, Krzysztof wrote:
> I don't understand :/ So what is solution in my case?
You could try :
PRAGMA temp_store=file;
immediately followed by:
PRAGMA temp_store=memory;
Please note:
http://sqlite.org/pragma.html#pragma_temp_store
I don't understand :/ So what is solution in my case?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On 28 Dec 2012, at 10:16pm, Krzysztof wrote:
> I thought about reopen connection (this would solve my problem in simple
> way) but my dependencies are tricky. I'm using free pascal which have
> TSQLite3Connection. This class handle sqlite connection, so I can attach
> multiple
I thought about reopen connection (this would solve my problem in simple
way) but my dependencies are tricky. I'm using free pascal which have
TSQLite3Connection. This class handle sqlite connection, so I can attach
multiple tables in the same session, so I can share temp tables between all
tables
On Fri, Dec 28, 2012 at 10:04 AM, Krzysztof wrote:
> Hi,
>
> I'm using PRAGMA temp_store=2 so all temp tables are created in memory. I
> have temp table with 1 000 000 000 records. Memory used by my test
> application grow up to ~80 MB. If I delete all records from this table or
>
You may be hitting the memory fragmentation issue. Try to run your
application with different memory managers (Hoard is my favorite -
http://www.hoard.org/) and see if the memory consumption is the same.
Also if you close all connections to your database (and other SQLite
databases too) does
On 28 Dec 2012, at 6:01pm, Krzysztof wrote:
> Can I call vacuum on custom tables (for example only on temp tables) ?
> Because vacuum takes some time (my "normal" tables are big and often
> modified, trim of those tables are not important for me) and I would like
> to free up
Can I call vacuum on custom tables (for example only on temp tables) ?
Because vacuum takes some time (my "normal" tables are big and often
modified, trim of those tables are not important for me) and I would like
to free up memory taken only by temp tables
On 28 Dec 2012, at 3:04pm, Krzysztof wrote:
> If I delete all records from this table or
> drop table, then my application still use 80 MB of memory. I have tried
> also PRAGMA shrink_memory. Why sqlite don't free memory?
SQLite does not free up space from a database until it
10 matches
Mail list logo