[sqlite] SQLite transaction time limit

[Paul]

You are probably asking for 


8 July 2015, 15:24:18, by "Iryna Atamanova" :

>   Hi guys,
> 
> I will be very appreciate for your help.
> 
> We have found the next feature of sqllite - it transaction takes more that
> 5 seconds, the database has been locked for some time. Could you please
> help us and let me know how we can increase this time - 5 seconds to 30 for
> example (what parameter / attribute can be used?)  from source code .
> 
> Our project is implemented on .Net CF and we use SQLite version 3.8.
> 
> Best regards,
> Ira Atamanova
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] SQLite transaction time limit

[Iryna Atamanova]

Hi guys,

I will be very appreciate for your help.

We have found the next feature of sqllite - it transaction takes more that
5 seconds, the database has been locked for some time. Could you please
help us and let me know how we can increase this time - 5 seconds to 30 for
example (what parameter / attribute can be used?)  from source code .

Our project is implemented on .Net CF and we use SQLite version 3.8.

Best regards,
Ira Atamanova

[sqlite] SIGSEGV rolling back in-memory DB‏‎

[Brian Soby]

Nothing appears to happen but it's not running very faithfully. Specifically, I 
get a bunch of problems on the rollbacks about the savepoints not existing even 
though it's replaying the original SAVEPOINT "x" command before the rollbacks. 
This is probably more due to me not knowing what's going on than anything else. 


> Date: Wed, 8 Jul 2015 10:19:17 -0700
> From: rogerb at rogerbinns.com
> To: sqlite-users at mailinglists.sqlite.org
> Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB??
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 07/08/2015 09:55 AM, Brian Soby wrote:
> > It's single threaded.
> 
> Good - that eliminates a whole bunch of complications.
> 
> > I have a log of all of the queries run through the database up
> > until the crash. It crashes on a rollback command.
> 
> What happens when you run those queries as a script for the SQLite
> shell?  If that has problems then everything needed to reproduce the
> issue is present.
> 
> However if that doesn't reproduce the issue then it is something else
> in the process that is causing problems.
> 
> Roger
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iEYEARECAAYFAlWdW5UACgkQmOOfHg372QTvJwCgrgS9gKjopjfppv6nPqTKSg1S
> rR4AoLwvAXooKJn/1kNwVipyEDwEQ0KZ
> =9y8e
> -END PGP SIGNATURE-
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] SQLite transaction time limit

[Kevin Benson]

http://permalink.gmane.org/gmane.comp.db.sqlite.general/91411

 'In the connection string, please use "Default Timeout"...'
*SNIP*
 'Also, the "Default Timeout" value is measured in seconds, so it would
be...'
*SNIP*

-> 30 in your case.

--
   --
  --
 --???--
K e V i N

On Wed, Jul 8, 2015 at 4:44 AM, Iryna Atamanova  wrote:

> Hi guys,
>
> I will be very appreciate for your help.
>
> We have found the next feature of sqllite - it transaction takes more that
> 5 seconds, the database has been locked for some time. Could you please
> help us and let me know how we can increase this time - 5 seconds to 30 for
> example (what parameter / attribute can be used?)  from source code .
>
> Our project is implemented on .Net CF and we use SQLite version 3.8.
>
> Best regards,
> Ira Atamanova
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] SIGSEGV rolling back in-memory DB‏‎

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/08/2015 09:55 AM, Brian Soby wrote:
> It's single threaded.

Good - that eliminates a whole bunch of complications.

> I have a log of all of the queries run through the database up
> until the crash. It crashes on a rollback command.

What happens when you run those queries as a script for the SQLite
shell?  If that has problems then everything needed to reproduce the
issue is present.

However if that doesn't reproduce the issue then it is something else
in the process that is causing problems.

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlWdW5UACgkQmOOfHg372QTvJwCgrgS9gKjopjfppv6nPqTKSg1S
rR4AoLwvAXooKJn/1kNwVipyEDwEQ0KZ
=9y8e
-END PGP SIGNATURE-

[sqlite] SIGSEGV rolling back in-memory DB‏‎

[Brian Soby]

It's single threaded. 
I have a log of all of the queries run through the database up until the crash. 
It crashes on a rollback command. Interestingly, I noticed that flattening my 
database migrations makes this issue go away so it may have something to do 
with schema changes and the journal.
I can send the log off-list to anyone who wants it. I could also send a 
dockerfile to recreate the problem. Any interest?

> Date: Tue, 7 Jul 2015 15:41:32 -0700
> From: rogerb at rogerbinns.com
> To: sqlite-users at mailinglists.sqlite.org
> Subject: Re: [sqlite] SIGSEGV rolling back in-memory DB??
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 07/07/2015 02:06 PM, Brian Soby wrote:
> > I don't believe it's a python specific issue since the core problem
> > occurs in a rollback command internal to SQLlite.
> 
> Unless you configure it otherwise, pysqlite likes to parse your SQL
> and do extra operations behind your back (eg automatically starting
> and committing transactions).  pysqlite also doesn't do
> multi-threading correctly - how do you do threading?
> 
> > I don't have an easy way to recreate the problem ...
> 
> That will make it very tricky.  Note that these kind of issues are
> extremely rare in SQLite, and almost always caused by other bits of
> code corrupting memory, and taking out SQLite as a side effect.  Try
> disabling as many non-SQLite extensions as possible (that are
> implemented in C).  Also use valgrind and similar tools as memory
> checkers.
> 
>   https://www.sqlite.org/testing.html
> 
> Sadly pysqlite doesn't have an easy way of tracing SQL execution
> without you modifying all call sites and updating its code to catch
> the behind your back operations.
> 
> If you have the time and can update your code, you can try APSW as an
> alternative to pysqlite (disclosure: I am the APSW author).  APSW
> includes a tool that lets you see all queries and data returned, as
> well as profiling information:
> 
>   http://rogerbinns.github.io/apsw/execution.html#apsw-trace
> 
> You may also find these two links relevant:
> 
>   http://rogerbinns.github.io/apsw/pysqlite.html
>   https://pythonhosted.org/sqmediumlite/src/apswdbapi2.py.html
> 
> Roger
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iEYEARECAAYFAlWcVZwACgkQmOOfHg372QSOjACgoSXRAijHJncTHYY6VU4dfB6Q
> gHIAoMT6zvydHZCvhNAFzX1azvFmMeZO
> =mfkI
> -END PGP SIGNATURE-
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users