Overview
Artifact ID: | 8c4f9d9c0dd1a1c6ab511418abc79da6039966e8a250f3ea9d7f2e911e17c57c |
---|---|
Ticket: | 265e935b26afe80fcceaff6c216484aa88d6c65e
FTS pgsz option results in "database disk image is malformed" error |
User & Date: | mrigger 2019-10-07 19:25:09 |
Changes
- foundin changed to: "3.30.0"
- icomment:
Consider the following test case: <pre> CREATE VIRTUAL TABLE vt0 USING fts5(a); PRAGMA reverse_unordered_selects = true; INSERT INTO vt0 VALUES('365062398'), (0), (0); INSERT INTO vt0(vt0, rank) VALUES('pgsz', '3'); UPDATE vt0 SET a = 399905135; -- unexpected: database disk image is malformed INSERT INTO vt1(vt1) VALUES('integrity-check'); </pre> The integrity-check indicates that the database disk image is malformed, which is unexpected. I suspect the reason to be an issue with the pgsz option. If, for example, the pgsz value is set to 3, then the UPDATE never terminates.
- login: "mrigger"
- mimetype: "text/x-fossil-wiki"
- severity changed to: "Critical"
- status changed to: "Open"
- title changed to:
FTS pgsz option results in "database disk image is malformed" error
- type changed to: "Code_Defect"