About a week ago, I posted this inside a response on another thread.
It may have gotten lost in the mix. Curious what folks think.
Considering things like bulk deletes (and updates) potentially really
growing a WAL file to be quite large along with having a system that
is constantly running and
On Sat Oct 23 20:57:56 GMT 2010, H. Phil Duby wrote:
> Give the described conditions, I do not think you need to worry about the
> WAL file growing without bound. I think that each increase should be
> smaller than the previous one, and will stop growing all together [for your
> stress test]
On Sat, Oct 23, 2010 at 5:56 AM, Richard Hipp wrote:
>
> Is that what you are seeing?
>
> Which filesystem are you using?
>
>
Thanks Richard, this does seem to be what I am seeing. I am definitely
seeing more writes during the subsequent cycles and an explanation
that this is likely due to the
I have been able to do some more investigation here. What I was seeing
originally made me suspicious that a writer was skipping over parts of the
WAL file during the time that a checkpoint is unable to proceed due to a
reader. After further investigation, however, I have determined that this is
> Are you *sure* you aren't accidentally holding a read transaction open
> somewhere?
> Do you have any other clues on how we can isolate the problem? A test case
> that will we can run here, perhaps?
A am pretty certain that I am not accidentally holding a read
transaction open. I have my
to when my writer process
can periodically close its database connection.
Does it sound like I have uncovered a concern here?
Thanks in advance,
Bob Smith
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
6 matches
Mail list logo
