Indeed it should, but currently does not. The problem here is that log_online_setup_bitmap_file_range() in log_online_purge_changed_page_bitmaps() does not include 3_200.xdb in the range as its start LSN falls outside, thus the range contains only one file 2_100.xdb, which is then not removed because it's the last in the range.
I am modifying the fix so that log_online_purge_changed_page_bitmaps() requests the range for 0..LSN_MAX instead of 0..lsn.That's suboptimal if there are many bitmap files, but the alternative of making log_online_setup_bitmap_file_range() to include one file past the range seems to be too complicated for a little benefit.
Andrew -
Indeed it should, but currently does not. The problem here is that log_online_ setup_bitmap_ file_range( ) in log_online_ purge_changed_ page_bitmaps( ) does not include 3_200.xdb in the range as its start LSN falls outside, thus the range contains only one file 2_100.xdb, which is then not removed because it's the last in the range.
I am modifying the fix so that log_online_ purge_changed_ page_bitmaps( ) requests the range for 0..LSN_MAX instead of 0..lsn.That's suboptimal if there are many bitmap files, but the alternative of making log_online_ setup_bitmap_ file_range( ) to include one file past the range seems to be too complicated for a little benefit.