Andrew Piskorski wrote:
On Sat, Apr 09, 2005 at 11:49:17AM -0400, Al Danial wrote:
Thanks to everyone who posted performance numbers and machine
setup info. Some results were counterintuitive (I'd have guessed
SCSI drives would come out on top) but many variables are at work
It is basically imp
Al Danial wrote:
The attached C program measures insert performance for populating
a table with an integer and three random floating point values with
user defined transaction size. Usage is:
./sqlite_insert
All of these are on Gentoo, Athlon 64 3200+, running 64 bit.
Writing to /tmp, whi
I can crash sqlite3 like this:
% cat test.sql
create table a (id INTEGER PRIMARY KEY);
alter table a add column f1 TEXT;
alter table a add column f2 TEXT;
alter table a add column f3 TEXT;
alter table a add column f4 TEXT;
alter table a add column f5 TEXT;
alter table a add column f6 TEXT;
alter ta
Assuming that users wait when SQLITE_BUSY is returned instead of just
giving up, a deadlock is possible. Let A and B be two users:
A: begin; select; insert;
B: begin; select;
B: insert; (busy, so waits and polls occasionally)
A: commit; (busy, so waits and polls occasionally)
Is there any plan t
4 matches
Mail list logo
