-
Aakanksha Verma authored
PROBLEM When using Index merge optimization current partitioning code in 5.6 does a memcpy instead of column of copy of the columns on which index read is done . Because of which wrong record gets copied and optimizer thinks there is no matching record as per the search criteria returning 0 for the count(*) value . The problem is sporiadic as the plan is not always using intersection . SOLUTION Added a similar column copy function that would do the copy of required column and not overwrite the other as in 5.7. Reviewed-by:
Debarun <Banerjee<debarun.banerjee@oracle.com> RB: 16157
Aakanksha Verma authoredPROBLEM When using Index merge optimization current partitioning code in 5.6 does a memcpy instead of column of copy of the columns on which index read is done . Because of which wrong record gets copied and optimizer thinks there is no matching record as per the search criteria returning 0 for the count(*) value . The problem is sporiadic as the plan is not always using intersection . SOLUTION Added a similar column copy function that would do the copy of required column and not overwrite the other as in 5.7. Reviewed-by:
Debarun <Banerjee<debarun.banerjee@oracle.com> RB: 16157
Loading