On 6/8/17, Tony Papadimitriou wrote:
> Does this also affect FOSSIL, or is auto vacuum never used there?
>
Fossil does not use auto_vacuum by default. So it probably does not affect it.
However, a sufficiently motivated Fossil administrator could use the
"fossil sql" command to
Does this also affect FOSSIL, or is auto vacuum never used there?
-Original Message-
From: D. Richard Hipp
Sent: Thursday, June 08, 2017 6:57 PM
To: sqlite-annou...@mailinglists.sqlite.org ;
sqlite-users@mailinglists.sqlite.org
Subject: [sqlite] Version 3.19.3 containing an important
On 6/8/17, Bob Friesenhahn wrote:
> On Thu, 8 Jun 2017, Richard Hipp wrote:
>>>
>>> We are using 3.17.0 (under Linux on 32-bit MIPS) and have been getting
>>> a database is corrupted report (as reported earlier to this list),
>>> with this call backtrace:
>>
>> The
On Thu, 8 Jun 2017, Richard Hipp wrote:
We are using 3.17.0 (under Linux on 32-bit MIPS) and have been getting
a database is corrupted report (as reported earlier to this list),
with this call backtrace:
The line numbers in the backtrace below do not align with version
3.17.0. Have you made
On 6/8/17, Bob Friesenhahn wrote:
> On Thu, 8 Jun 2017, D. Richard Hipp wrote:
>
>> A bug in the auto_vacuum logic for SQLite versions 3.16.0 through
>> 3.19.2 can (rarely) lead to database corruption. SQLite version
>> 3.19.3 has just been released to fix this bug.
On Thu, 8 Jun 2017, D. Richard Hipp wrote:
A bug in the auto_vacuum logic for SQLite versions 3.16.0 through
3.19.2 can (rarely) lead to database corruption. SQLite version
3.19.3 has just been released to fix this bug.
Does 'pragma integrity_check' reliably detect this database
A bug in the auto_vacuum logic for SQLite versions 3.16.0 through 3.19.2 can
(rarely) lead to database corruption. SQLite version 3.19.3 has just been
released to fix this bug.
https://sqlite.org/
https://sqlite.org/download.html
See https://www.sqlite.org/src/info/fda22108 for more
7 matches
Mail list logo