[Bug 1193177] sqlite3_drv bad memory free and severe performance bug - with patch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1193177



--- Comment #7 from Stuart D Gathman <stuart@xxxxxxxxxxx> ---
After doing some more reading on sqlite3 transactions, I believe the BEGIN
should be a BEGIN IMMEDIATE.  

With the plain BEGIN, locks are deferred until the actual query or update - and
the COMMIT may fail with SQLITE_BUSY, and need to be retried (with potential
deadlock).

With BEGIN IMMEDIATE, RESERVED locks (allow others to read, but not write) are
acquired on the database immediately.  The BEGIN IMMEDIATE may then fail, and
should return an error (or does it need to loop?), but the COMMIT should be ok
once the BEGIN IMMEDIATE succeeds.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=1OkL0RlBr6&a=cc_unsubscribe
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/perl-devel





[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Legacy Announce]     [Fedora PHP Devel]     [Kernel Devel]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite Information]
  Powered by Linux