{"push_id":1358760872,"size":2,"distinct_size":2,"ref":"refs/heads/gh-1697-vy-speedup-recovery","head":"561032bde10183e7973dc8c393c691b7d89d8735","before":"54e6f47db9a245ac035ea182bf9976b904ed7f89","commits":[{"sha":"eaec1817d1b9b8b7f6ec6fa24b907a13bf356eb2","author":{"name":"Vladimir Davydov","email":"1721f5af41d5faac84cf50f6b799e8df07d9cf07@gmail.com"},"message":"vinyl: handle eq order in range iterator\n\nWhenever we need VINYL_EQ order in range iterator, we use VINYL_GE.\nThis behavior exists solely due to historical reasons and needs to\nbe fixed.","distinct":true,"url":"https://api.github.com/repos/tarantool/tarantool/commits/eaec1817d1b9b8b7f6ec6fa24b907a13bf356eb2"},{"sha":"561032bde10183e7973dc8c393c691b7d89d8735","author":{"name":"Vladimir Davydov","email":"1721f5af41d5faac84cf50f6b799e8df07d9cf07@gmail.com"},"message":"vinyl: eliminate reads on recovery\n\nCurrently, we use a rather dumb way to determine if a statement from\nxlog should be committed or not on recovery - we lookup the statement in\nall on-disk runs and, if found, compare its lsn. Obviously, this slows\ndown the recovery procedure significantly. Actually, we can avoid\nreading on-disk runs altogether. All we need to do is compare the xlog\nstatement's lsn with the range's max lsn - we should only commit the\nstatement if the former is greater.\n\nCloses #1697","distinct":true,"url":"https://api.github.com/repos/tarantool/tarantool/commits/561032bde10183e7973dc8c393c691b7d89d8735"}]}
{"actor":{"display_login":"locker"}}