Daniel Polski wrote:
> Can using "PRAGMA optimize" in one thread create a situation where
> "BEGIN IMMEDIATE TRANSACTION" in another thread fails?
While the optimization is done, the database is locked, just as with
any other transaction that does writes. So any other thread has to use
a timeout.
Den 2017-03-24 kl. 08:09, skrev Daniel Polski:
The "PRAGMA optimize" looks interesting.
- Can using "PRAGMA optimize" in one thread create a situation where
"BEGIN IMMEDIATE TRANSACTION" in another thread fails? (The threads
are using different connections)
- Is there any risk of "optimizati
On 03/24/2017 02:43 PM, no...@null.net wrote:
On Fri Mar 24, 2017 at 08:31:13AM +0100, no...@null.net wrote:
On Thu Mar 23, 2017 at 07:50:34PM -0400, Richard Hipp wrote:
The second beta release for SQLite 3.18.0 is now available on the website:
I see the following issue:
Program terminat
On Fri Mar 24, 2017 at 08:31:13AM +0100, no...@null.net wrote:
> On Thu Mar 23, 2017 at 07:50:34PM -0400, Richard Hipp wrote:
> > The second beta release for SQLite 3.18.0 is now available on the website:
>
> I see the following issue:
>
> Program terminated with signal SIGSEGV, Segmentation
On Thu Mar 23, 2017 at 07:50:34PM -0400, Richard Hipp wrote:
> The second beta release for SQLite 3.18.0 is now available on the website:
>
>https://www.sqlite.org/download.html
I see the following issue:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 sqlite3VdbeExec
The "PRAGMA optimize" looks interesting.
- Can using "PRAGMA optimize" in one thread create a situation where
"BEGIN IMMEDIATE TRANSACTION" in another thread fails? (The threads are
using different connections)
- Is there any risk of "optimization fighting" if several threads are
using the s
6 matches
Mail list logo
