are you saying this is a memory leak?
sqlite never gives back the unused memory?
Christian Smith wrote:
Lokesh Babu uttered:
Hello Folks,
When I perform the DELETE operation on a Table using In-Memory Database
(":memory:"), the memory usage increases.
I tried using PRAGMA auto_vacuum=1; /* result - nothing works */
Even I tried using VACUUM table_name; /* this too isn't work */
if I perform DROP the table operation, memory usage works. Deleting
the rows
doesn't work.
Anybody please help me in resolving this.
Memory usage goes up because SQLite must temporarily store copies of
the old pages that store the deleted rows, in order to allow a future
rollback if required.
Once a commit is done, the old pages are free'd, but by that time the
memory footprint has already increased. Not many libc implementations
release heap memory back to the OS once it's allocated.
Thanks in advance,
Lokee
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
--
-
As nightfall does not come at once, neither does oppression. In both
instances, there is a twilight when everything remains seemingly unchanged. And
it is in such twilight that we all must be most aware of change in the air
however slight lest we become unwitting victims of the darkness.
William O. Douglas, Justice of the U.S. Supreme Court
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
