Improve Index Recovery Algorithm

[Hedgemon4]

Description

• Improve the index file recovery algorithm with the base data file recovery algorithm changes to ensure durability and functions with non-file-based storage mediums.
• Add the ability to regenerate the indices lost when the database crashes but were already written to permanent storage in the fixed data file.

[github-actions]

Makefile Ubuntu Unit Test Results

  1 files  ±0   14 suites  ±0   0s ⏱️ ±0s
105 tests +7  104 ✅ +6  0 💤 ±0  1 ❌ +1 
131 runs  +7  130 ✅ +6  0 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit 5254127. ± Comparison against base commit ef0416b.

This pull request removes 1 and adds 8 tests. Note that renamed tests count towards both.

test_embedDB_index_recovery ‑ embedDB_index_file_correctly_reloads_with_eleven_pages_of_data

test_embedDB_index_recovery ‑ embedDBFlush_should_not_flush_index_pages
test_embedDB_index_recovery ‑ embedDBIndexRecovery_should_recover_indicies_in_buffer_with_21_pages_of_data_written
test_embedDB_index_recovery ‑ embedDBIndexRecovery_should_recover_indicies_in_buffer_with_no_index_pages_written
test_embedDB_index_recovery ‑ embedDBIndexRecovery_should_recover_indicies_in_buffer_with_sixteen_pages_of_data_written
test_embedDB_index_recovery ‑ embedDBIndexRecovery_should_recover_indicies_in_buffer_with_with_seven_pages_written
test_embedDB_index_recovery ‑ embedDB_index_file_correctly_reloads_with_eight_pages_of_data
test_embedDB_index_recovery ‑ embedDB_index_file_correctly_reloads_with_seventeen_pages_of_data
test_embedDB_index_recovery ‑ embedDB_index_file_correctly_reloads_with_sixteen_pages_of_data

♻️ This comment has been updated with latest results.

[github-actions]

PlatformIO Ubuntu Unit Test Results

  1 files  ±0   84 suites  ±0   13s ⏱️ ±0s
105 tests +7  105 ✅ +7  0 💤 ±0  0 ❌ ±0 
131 runs  +7  131 ✅ +7  0 💤 ±0  0 ❌ ±0 

Results for commit 3247d81. ± Comparison against base commit ef0416b.

This pull request removes 1 and adds 8 tests. Note that renamed tests count towards both.

embedDB_index_file_correctly_reloads_with_eleven_pages_of_data

embedDBFlush_should_not_flush_index_pages
embedDBIndexRecovery_should_recover_indicies_in_buffer_with_21_pages_of_data_written
embedDBIndexRecovery_should_recover_indicies_in_buffer_with_no_index_pages_written
embedDBIndexRecovery_should_recover_indicies_in_buffer_with_sixteen_pages_of_data_written
embedDBIndexRecovery_should_recover_indicies_in_buffer_with_with_seven_pages_written
embedDB_index_file_correctly_reloads_with_eight_pages_of_data
embedDB_index_file_correctly_reloads_with_seventeen_pages_of_data
embedDB_index_file_correctly_reloads_with_sixteen_pages_of_data

♻️ This comment has been updated with latest results.