Re: [sqlite] Tracing latencies

On 12/05/2012 09:22 AM, Keith Chew wrote: On Wed, Dec 5, 2012 at 1:14 PM, Keith Chew wrote: Since there is no fsync (I know this using grep on the strace ouput), it is hard to tell what to look for in the strace. The output is very noisy, so it makes it hard to go through

Re: [sqlite] Tracing latencies

On Wed, Dec 5, 2012 at 1:14 PM, Keith Chew wrote: > Since there is no fsync (I know this using grep on the strace ouput), > it is hard to tell what to look for in the strace. The output is very > noisy, so it makes it hard to go through them. > > Does anyone know any handy

Re: [sqlite] Tracing latencies

Hi Michael On Wed, Dec 5, 2012 at 12:02 PM, Black, Michael (IS) wrote: > Can you re-run your strace as "strace -tt" and look at the timings to help > pinpoint it? Since there is no fsync (I know this using grep on the strace ouput), it is hard to tell what to look for

Re: [sqlite] Bug: Segmentation fault in libsqlite3.so.0.8.6[b69a4000+ac000]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/12/12 14:43, Paul Menzel wrote: > The following code caused the segmentation fault. By far the most likely cause is some other library or the app itself stomping on SQLite's memory. SQLite is on every Android device, every iOS device,

Re: [sqlite] Tracing latencies

Can you re-run your strace as "strace -tt" and look at the timings to help pinpoint it? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems From:

Re: [sqlite] Bug: Segmentation fault in libsqlite3.so.0.8.6[b69a4000+ac000]

On 4 December 2012, Paul Menzel wrote: After doing `apt-get source sqlite3` and building it myself with `debuild -b -us -uc`, I have the source file `sqlite3.c` and I am able to look at the code statements. > The backtrace from the core dump file is the following. > > Thread 1 (Thread

Re: [sqlite] Tracing latencies

On Wed, Dec 5, 2012 at 11:10 AM, Keith Chew wrote: > The strange thing is that I am setting sqlite it to use WAL, > autocheckpoint off and synchronous off. Even in this setup, I still > see > 350ms transactions times for less than 3 TPS. A bit hard to > believe, so I am now

Re: [sqlite] Bug: Segmentation fault in libsqlite3.so.0.8.6[b69a4000+ac000]

Am Sonntag, den 02.12.2012, 22:49 +0100 schrieb Paul Menzel: > using Debian Sid/unstable with self-built Evolution 3.4.4 and > libsqlite3-0 3.7.14.1-1, Evolution crashed with a segmentation fault. > > pool[15522]: segfault at 5 ip b69bafe3 sp 8acf0850 error 6 in >

Re: [sqlite] Tracing latencies

Hi Michael On Wed, Dec 5, 2012 at 10:57 AM, Black, Michael (IS) wrote: > Could it be waitiing on the prior transaction though? > > Since disk I/O lies it might be syncing the last transaction causing the new > one to wait longer. Yes, that is possible. In the

Re: [sqlite] Tracing latencies

On Wed, Dec 5, 2012 at 10:56 AM, Richard Hipp wrote: >> It is not an indexing issue. For one of the UPDATE SQLs, it is >> updating a table with only 1 record in it. And this takes > 350ms... >> > > Can you provide specifics: The schema and the UPDATE statement? Schema and SQL

Re: [sqlite] Tracing latencies

Could it be waitiing on the prior transaction though? Since disk I/O lies it might be syncing the last transaction causing the new one to wait longer. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems

Re: [sqlite] Tracing latencies

On Tue, Dec 4, 2012 at 4:45 PM, Keith Chew wrote: > On Wed, Dec 5, 2012 at 10:28 AM, Keith Chew wrote: > > > > I wonder what could be causing sqlite to hang so long? Will try to > > remove all indexes to see if that narrows things down. > > It is not

Re: [sqlite] Tracing latencies

On Wed, Dec 5, 2012 at 10:28 AM, Keith Chew wrote: > > I wonder what could be causing sqlite to hang so long? Will try to > remove all indexes to see if that narrows things down. It is not an indexing issue. For one of the UPDATE SQLs, it is updating a table with only 1

Re: [sqlite] Async IO in SQLite 3.7.15

On 04.12.2012 22:25, Richard Hipp wrote: >> My question is if existing applications which Async IO should continue >> to work with SQLite 3.7.15? Or has something in the SQLite core changed >> so that you'd expect Async IO failures in 3.7.15, or later versions? > > They should continue to work,

Re: [sqlite] Tracing latencies

On Wed, Dec 5, 2012 at 9:33 AM, Keith Chew wrote: > Any other ideas for me to trace this at a lower level would be greatly > appreciated. I think I will need to get deeper into linux's block > layer stuff, so perhaps this is not the correct place to ask the > question, but I

Re: [sqlite] Async IO in SQLite 3.7.15

On Tue, Dec 4, 2012 at 4:20 PM, Ralf Junker wrote: > On 04.12.2012 22:14, Richard Hipp wrote: > > >> Does this also mean that it will no longer be working with SQLite > >> 3.7.15? Is it just deprecated for new development? Or has something else > >> changed that I should take

Re: [sqlite] Async IO in SQLite 3.7.15

On 04.12.2012 22:14, Richard Hipp wrote: >> Does this also mean that it will no longer be working with SQLite >> 3.7.15? Is it just deprecated for new development? Or has something else >> changed that I should take care of? > > That means that we are not willing to devote large amounts of time

Re: [sqlite] Async IO in SQLite 3.7.15

On Tue, Dec 4, 2012 at 4:11 PM, Ralf Junker wrote: > I experience problems with Async IO testing the latest 3.7.15 trunk. > Simple statements like CREATE TABLE fail with SQLITE_IOERR. > > I read the note in the Async IO README.txt that Async IO is now > superceded by WAL mode

[sqlite] Async IO in SQLite 3.7.15

I experience problems with Async IO testing the latest 3.7.15 trunk. Simple statements like CREATE TABLE fail with SQLITE_IOERR. I read the note in the Async IO README.txt that Async IO is now superceded by WAL mode and no longer maintained. Does this also mean that it will no longer be working

Re: [sqlite] .dump ... [was: Please test the latest SQLite snapshot]

On 3 Dec 2012, Richard Hipp wrote: ... You can get a tarball or ZIP archive of the latest raw sources from Fossil at http://www.sqlite.org/src/info/trunk I notice that in this (3.7.15 pre-release snapshot) version of the shell the .help out for the .dump command reads: .dump ?TABLE? ...

Re: [sqlite] Tracing latencies

Hi Richard On Wed, Dec 5, 2012 at 9:05 AM, Richard Hipp wrote: > The $dir will contain initial database contents and scripts of SQL > statements that were run. You can rerun those SQL statement using the > command-line shell to find slow ones, then do things like EXPLAIN QUERY

Re: [sqlite] Tracing latencies

On Tue, Dec 4, 2012 at 2:30 PM, Keith Chew wrote: > Hi > > I have an existing application, which I am experimenting with > replacing MySQL with sqlite. I have 2 boxes, one running MySQL, the > other sqlite. > > Execution times for every insert/update/delete SQLs is

[sqlite] Tracing latencies

Hi I have an existing application, which I am experimenting with replacing MySQL with sqlite. I have 2 boxes, one running MySQL, the other sqlite. Execution times for every insert/update/delete SQLs is measured, and a warn log is printed if it takes > 250ms to perform the SQL. OS configuration:

Re: [sqlite] Bug: Segmentation fault in libsqlite3.so.0.8.6[b69a4000+ac000]

On Tue, Dec 4, 2012 at 9:35 AM, Paul Menzel < paulepan...@users.sourceforge.net> wrote: > > Could this please be added to the bug tracker? Unfortunately this > backtrace is all I have got. > Just because SQLite appears in a stack trace does not mean that SQLite is at fault here. In fact, far

Re: [sqlite] Bug: Segmentation fault in libsqlite3.so.0.8.6[b69a4000+ac000]

Dear SQLite folks, Am Sonntag, den 02.12.2012, 22:49 +0100 schrieb Paul Menzel: > using Debian Sid/unstable with self-built Evolution 3.4.4 and > libsqlite3-0 3.7.14.1-1, Evolution crashed with a segmentation fault. > > pool[15522]: segfault at 5 ip b69bafe3 sp 8acf0850 error 6 in >

[sqlite] Test failures on Ubuntu

Hi, I am getting failures in the below tests while doing the regression test on Ubuntu with , SHA1 Hash: ba8d08b67021a32fda069c18b7eb93523e6f0d1f Date: 2012-11-27 21:56:28 Most of the failures are, Expected: [1 1] Got: [0 {}] Are these errors serious, How to fix these ? Thank You

[sqlite] FW: Invalid Code gemerated for Virtual Table Join with OR clause

Von: Hick Gunter Gesendet: Montag, 03. Dezember 2012 15:28 An: 'Richard Hipp' Betreff: AW: [sqlite] Invalid Code gemerated for Virtual Table Join with OR clause Thank you for your reply. As indicated in the second message, I have located the code where the

Re: [sqlite] Another example of windows users needing help. Fwd: sqlite.dll

@Richard; What kind of support are you supposed to be giving users? sqlite3.dll is a DLL, not an application, and without looking at the source code, I know for certain the DLL itself isn't asking someone to download something else, ASSUMING of course, its a precompiled version from sqlite.org

Re: [sqlite] Another example of windows users needing help. Fwd: sqlite.dll

It's not easy being an incon On 4 December 2012 10:44, Richard Hipp wrote: > Here is another example of the kind of email I get on a regular basis. > > Note that I also get phone calls about this. Sometimes at odd hours. > > -- Forwarded message -- > From: Åke

Re: [sqlite] Result of multi-command _exec() that errors ?

On 4 Dec 2012, at 11:13am, Simon Davies wrote: > 3rd paragraph: > "If an error occurs while evaluating the SQL statements passed into > sqlite3_exec(), then execution of the current statement stops and > subsequent statements are skipped." Dammit. Missed it.

Re: [sqlite] Result of multi-command _exec() that errors ?

On 4 December 2012 11:02, Simon Slavin wrote: > (Yes, I know I should be preparing and binding for security reasons, but that > doesn't work here.) > > What is the result when using _exec() on multiple statements when one of the > statements errors ? I read this page: > >

[sqlite] Result of multi-command _exec() that errors ?

(Yes, I know I should be preparing and binding for security reasons, but that doesn't work here.) What is the result when using _exec() on multiple statements when one of the statements errors ? I read this page: and I can't figure out whether

Re: [sqlite] "SQLite not working on windows". Fwd: download

On 4 Dec 2012, at 10:42am, Richard Hipp wrote: > I get a lot of inquiries like this from windows users. They get some kind > of dialog box about an SQLite3.dll not being found or being out-of-date. > It might be good to create a webpage of some sort to try to help them, but >

[sqlite] Another example of windows users needing help. Fwd: sqlite.dll

Here is another example of the kind of email I get on a regular basis. Note that I also get phone calls about this. Sometimes at odd hours. -- Forwarded message -- From: Åke Halvarson Date: Tue, Dec 4, 2012 at 5:22 AM Subject: sqlite.dll To:

[sqlite] "SQLite not working on windows". Fwd: download

I get a lot of inquiries like this from windows users. They get some kind of dialog box about an SQLite3.dll not being found or being out-of-date. It might be good to create a webpage of some sort to try to help them, but I don't know what to put on that webpage. Does anybody have any

Re: [sqlite] what diffrent with this two sql command?

... SELECT b FROM mytable WHERE b = c will give you each row of the database which has identical b and c values. ... SELECT b FROM mytable AS m2 WHERE m2.b = m1.c will join the two views of the database together, so if mytable contains b,c 1,2 2,3 the combined table for this subquery looks like: