Abhishek Kona d68880a1b9 Do not allow Transaction Log Iterator to fall ahead when writer is writing the same file ... Summary: Store the last flushed, seq no. in db_impl. Check against it in transaction Log iterator. Do not attempt to read ahead if we do not know if the data is flushed completely. Does not work if flush is disabled. Any ideas on fixing that? * Minor change, iter->Next is called the first time automatically for * the first time. Test Plan: existing test pass. More ideas on testing this? Planning to run some stress test. Reviewers: dhruba, heyongqiang CC: leveldb Differential Revision: https://reviews.facebook.net/D9087		2013-03-06 14:05:53 -08:00
..
shell	Titile: a command line shell to read/write data from a leveldb thrift server	2012-08-23 09:41:05 -07:00
db_repl_stress.cc	Do not allow Transaction Log Iterator to fall ahead when writer is writing the same file	2013-03-06 14:05:53 -08:00
db_stress.cc	Refactor statistics. Remove individual functions like incNumFileOpens	2013-02-25 13:58:34 -08:00
ldb_test.py	Enhanced ldb to support data access commands	2013-01-28 11:38:26 -08:00
ldb.cc	Enhanced ldb to support data access commands	2013-01-28 11:38:26 -08:00
manifest_dump.cc	manifest_dump: Fix the help message and make it consistent	2012-12-21 10:45:24 -08:00
reduce_levels_test.cc	Enhanced ldb to support data access commands	2013-01-28 11:38:26 -08:00
sst_dump.cc	Fix a number of object lifetime/ownership issues	2013-01-23 16:54:11 -08:00