https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Fedora Update System changed:
What|Removed |Added
Fixed In Version|dspam-3.10.2-10.el7 |dspam-3.10.2-6.el6
--- Comment
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Fedora Update System changed:
What|Removed |Added
Fixed In Version|dspam-3.10.2-16.fc20|dspam-3.10.2-10.el7
--- Commen
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Fedora Update System changed:
What|Removed |Added
Fixed In Version|dspam-3.10.2-16.fc21|dspam-3.10.2-16.fc20
--- Comme
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #12 from Stuart D Gathman ---
Short answer: I do not have a revised patch
Long answer:
My reading of the docs is that because there is only one table involved, the
existing patch should work. If there is a lock failure, it will f
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #11 from Nathanael Noblet ---
So I don't use the sqlite driver so don't have any skin in this game. It looks
like they've committed your patch upstream however you don't seem to be sure
its the best way forward. If I push these bui
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #10 from Stuart D Gathman ---
However, there is just one table immediately updated (no reads between BEGIN
and UPDATE/INSERT). If that update fails to obtain the lock, we error out
correctly with a rollback. There can be no deadl
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #9 from Stuart D Gathman ---
https://www.sqlite.org/lang_transaction.html
--
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=aYRArAe4Rp&a
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #8 from Stuart D Gathman ---
I have not seen this potential problem, and multiprocess test cases are hard to
construct. Dspam has its own lock file, which may prevent other dspam
processes from tripping up the transaction.
--
Yo
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #7 from Stuart D Gathman ---
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
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Stevan Bajić changed:
What|Removed |Added
CC||ste...@bajic.ch
--- Comment #6 from St
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #5 from Fedo
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #3 from Fedora Update System ---
dspam-3.10.2-10.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/dspam-3.10.2-10.el7
--
You are receiving this mail because:
You are on the CC list fo
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #4 from Fedora Update System ---
dspam-3.10.2-6.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/dspam-3.10.2-6.el6
--
You are receiving this mail because:
You are on the CC list for
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #2 from Fedora Update System ---
dspam-3.10.2-16.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/dspam-3.10.2-16.fc21
--
You are receiving this mail because:
You are on the CC list for
https://bugzilla.redhat.com/show_bug.cgi?id=1193177
--- Comment #1 from Fedora Update System ---
dspam-3.10.2-16.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/dspam-3.10.2-16.fc20
--
You are receiving this mail because:
You are on the CC list for
16 matches
Mail list logo
