The setting for synchronous is basically what level of safety net do you want if it dies in the middle of something. Setting it to off shouldn't cause any corruption if things go well, it should only come into play if you saw errors or didn't close things down correctly etc.
The unique index you declared is redundant by the way, declaring those three fields as the primary key makes a unique index already to keep track of that. Did you intend to make that on the retry table? -----Original Message----- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Fiona Sent: Sunday, October 15, 2017 9:15 PM To: sqlite-users@mailinglists.sqlite.org Subject: Re: [sqlite] Sqlite3.6 Command-line delete/update not working with large db file(>280GB) Thanks a lot! That may be the problem: my db file is corrupted. Below is the *PRAGMA integrity_check* result. It didn't return OK. <http://sqlite.1065341.n5.nabble.com/file/t8403/integrity_check.jpg> I think it's because I set PRAGMA synchronous=off in Python code to enhance insert speed. Does that mean this db file can not be used anymore? Or is there any way I can fix it? -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
