search for: concurrernt

...that in theory, SQLite3 should be able to atomically lock the file (or a subset of page), modify pages, flush the pages to gluster, then release the lock, and thus satisfy the ACID property that SQLite3 appears to try to accomplish on a local filesystem. In a test we wrote that fires off 10 simple concurrernt SQL insert, read, update loops, we discovered that we at least need to use flock() around the SQLite3 db connection open/update/close to protect it. However, that is not enough - although from testing, it looks like flock() works as advertised across gluster mounted files, sync/fsync don't app...

...d > be able to atomically lock the file (or a subset of page), modify > pages, flush the pages to gluster, then release the lock, and thus > satisfy the ACID property that SQLite3 appears to try to accomplish on > a local filesystem. > > In a test we wrote that fires off 10 simple concurrernt SQL insert, > read, update loops, we discovered that we at least need to use flock() > around the SQLite3 db connection open/update/close to protect it. > > However, that is not enough - although from testing, it looks like > flock() works as advertised across gluster mounted files,...

...omically lock the file (or a subset of page), modify >> pages, flush the pages to gluster, then release the lock, and thus >> satisfy the ACID property that SQLite3 appears to try to accomplish on >> a local filesystem. >> >> In a test we wrote that fires off 10 simple concurrernt SQL insert, >> read, update loops, we discovered that we at least need to use flock() >> around the SQLite3 db connection open/update/close to protect it. >> >> However, that is not enough - although from testing, it looks like >> flock() works as advertised across glu...

...r a subset of page), modify > >> pages, flush the pages to gluster, then release the lock, and thus > >> satisfy the ACID property that SQLite3 appears to try to accomplish on > >> a local filesystem. > >> > >> In a test we wrote that fires off 10 simple concurrernt SQL insert, > >> read, update loops, we discovered that we at least need to use flock() > >> around the SQLite3 db connection open/update/close to protect it. > >> > >> However, that is not enough - although from testing, it looks like > >> flock() works...

...modify >> >> pages, flush the pages to gluster, then release the lock, and thus >> >> satisfy the ACID property that SQLite3 appears to try to accomplish on >> >> a local filesystem. >> >> >> >> In a test we wrote that fires off 10 simple concurrernt SQL insert, >> >> read, update loops, we discovered that we at least need to use flock() >> >> around the SQLite3 db connection open/update/close to protect it. >> >> >> >> However, that is not enough - although from testing, it looks like >> &g...

...pages, flush the pages to gluster, then release the lock, and thus > >> >> satisfy the ACID property that SQLite3 appears to try to accomplish > on > >> >> a local filesystem. > >> >> > >> >> In a test we wrote that fires off 10 simple concurrernt SQL insert, > >> >> read, update loops, we discovered that we at least need to use > flock() > >> >> around the SQLite3 db connection open/update/close to protect it. > >> >> > >> >> However, that is not enough - although from testing,...

...ges to gluster, then release the lock, and thus >> >> >> satisfy the ACID property that SQLite3 appears to try to accomplish >> on >> >> >> a local filesystem. >> >> >> >> >> >> In a test we wrote that fires off 10 simple concurrernt SQL insert, >> >> >> read, update loops, we discovered that we at least need to use >> flock() >> >> >> around the SQLite3 db connection open/update/close to protect it. >> >> >> >> >> >> However, that is not enough - alt...