[MDEV-19870] gcol.innodb_virtual_debug_purge doesn't fail if row_vers_old_has_index_entry gives wrong result Created: 2019-06-26  Updated: 2019-07-24  Resolved: 2019-07-24

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2
Fix Version/s: 10.2.26, 10.3.17, 10.4.7

Type: Bug Priority: Major
Reporter: Thirunarayanan Balathandayuthapani Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None

Attachments: File unsafe_to_purge.patch    

 Description   

The attached patch changes the value returned for row_vers_old_has_index_entry().
But there is no failure with the virtual column test case. Write a valid test case and
improve the coverage.



 Comments   
Comment by Marko Mäkelä [ 2019-07-24 ]

The problem turned out to not affect functionality. The code was confusing, because a wrong value was being returned from a function. But, the caller ignored this value in the affected code paths.

Generated at Thu Feb 08 08:54:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.