> Le 24 mars 2016 ? 14:46, Domingo Alvarez Duarte dev.dadbiz.es> a ?crit :
>
> But in this example there is only one application accessing the database and
> only one table with one small record been updated all the time and no active
> readers, why it's writing to wal ?
Because it is
not update the same record instead of adding a new one in such
situation ?
I'll try with a bigger record to see what happens.
Cheers !
?
> Thu Mar 24 2016 11:55:11 AM CET from "Domingo Alvarez Duarte"
> Subject: [sqlite] SQLite with wall enabled
>what's wron
Thanks for reply !
The error check was left out intentionally to not pollute the code, I stepped
through all code with gdb to certify it's doing all correctly.
Cheers !
> Thu Mar 24 2016 12:03:28 PM CET from "Stephan Beal"
> Subject: Re: [sqlite] SQLite with wall enabled
On Thu, Mar 24, 2016 at 11:55 AM, Domingo Alvarez Duarte <
sqlite-mail at dev.dadbiz.es> wrote:
> There is something wrong with the program or with sqlite3 ?
>
>
> rc = sqlite3_bind_text(stmt_insert, 1, session_id,
> sizeof(session_id)-1, NULL);
> rc =
Hello !
I'm sending here a C program that demonstrates the problem of sqlite3 in wall
mode,
in this simple example of a simulated session management for a web server
when executing
the wall log file will grow and grow till eat all our disk.
?
There is something wrong with the
Hello Simon !
Thanks again for reply !
Yes I do _prepare(), _bind(), _step(), _reset() | _step(), _finalize(), you
can see it on the source code I posted on the first post.
Cheers !
> Thu Mar 24 2016 12:21:44 AM CET from "Simon Slavin"
> Subject: Re: [sqlite] SQLite w
Hello !
Thanks for reply !
I'm using prepared statements and "sqite3_step == SQLITE_ROW" undeer
"stmt.next_row()".
Cheers !
> Thu Mar 24 2016 12:13:22 AM CET from "Simon Slavin"
> Subject: Re: [sqlite] SQLite with wall enabled
>what's
>wr
On 23 Mar 2016, at 11:43pm, Domingo Alvarez Duarte wrote:
> Yes I do _prepare(), _bind(), _step(), _reset() | _step(), _finalize(), you
> can see it on the source code I posted on the first post.
Okay, I don't know your programming language so this has to wait for someone
who does.
Simon.
Hello again !
After all my tests I conclude that the actuall implementation of sqlite
"wall" mode
needs active manual management to not grow unbounded and with
multiuser/long running proesses sharing the same database
sqlite will eat all our disk space, because the chance of a process
get the
r-- 1 ? 562626560 Mar 23 22:26 hacker-news-items-diff.db
//550MB db with all users and users_submitted
?
> Wed Mar 23 2016 11:10:56 PM CET from "Domingo Alvarez Duarte"
> Subject: [sqlite] SQLite with wall enabled
>what's wrong
>
> Hello !
>
> Can som
On 23 Mar 2016, at 11:18pm, Domingo Alvarez Duarte wrote:
> I'm using prepared statements and "sqite3_step == SQLITE_ROW" undeer
> "stmt.next_row()".
Which programming language/environment are you using ?
When you are finished with your statements are you finalizing them ?
_prepare()
_step,
How are you executing your SQLite calls ? Are you using _step() or _exec() ?
Are you using SQLite calls directly or using a database library ?
Are you doing your INSERT calls in a transaction ?
Simon.
Hello !
Can someone give any insight here ?
For me the main problem is the wall size that becomes stable at 387MB (+- 8%
of the database, but around 15 times the size of the tables it's
manipulating).
It seems to me that something is not working as advertised.
I'm testing sqlite3 with
13 matches
Mail list logo
