meanwhile i'm guessing that there's a total of 3 extra checks that complicate 
it a little:
- checking if a disk space threshold is reached, which involves maintain a 
count of sparse usage
- checking if holes on the left of cached fetches are filled showing that the 
held pagesize is mismatching behavior
- checking if holes on the right of cached fetches are filled, data for these 
can be fetched
it might make sense to just assert for the second 2 checks to simplify the code 
and encourage more robust page sizing

Reply via email to