I don't know if this applies to SQLite, but many database systems have a problem if you fork after connecting; In this case, forking first and then connecting to the database (or if that's not an option, reconnect in the child process after fork) is the proper solution.
In reply to Re: Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager
by moritz
in thread Unexpected and uncatchable database corruption errors using DBD::SQLite & Parallel::ForkManager
by djerius
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |