On Tue, Feb 23, 2021 at 01:19:24PM -0500, Wietse Venema wrote: > > > Yes, it does, but the way it ?deals? with it is to throw an error > > if one connection tried to read while another is writing. The net > > Bleh, it does not retry the operation?
Only if you specify a retry timeout. SQLite is mostly for embedded use-cases, and support for sharing has warts. > What happens when you update the table while some Postfix code is > READING from the DB? Does the writer also fail? No, only if the writer has no retry timeout. This typically works, but is sub-optimal. > > It would be nice if postfix would set a non-zero busy timeout. > > It?s a simple code change, just a call to sqlite3_busy_timeout. > > What about https://www.sqlite.org/pragma.html#pragma_busy_timeout ? > I don't know if that is a DB property or a session property. It is a session property. > If we take this route, then there needs to be a new field in the > Postfix sqlite config file that controls the time limit. Yes. -- Viktor.
