Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.5.11, 10.5.12, 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL)
-
None
-
Centos7
Description
There is a bug with split_materialized.
When optimizer_switch='split_materialized=on'; the attached query returns very wrong results. After disabling the split_materialized, it returns the correct results.
This bug starts in 10.5.10, which is the version that includes the fixes from 10.4.19. 10.4.19 includes MDEV-25128 fix which could be a blame option. The bug does not happen in 10.5.9.
I've attached the .sql to reproduce the bug.
Attachments
Issue Links
- duplicates
-
MDEV-27132 Wrong result from query when using split optimization
- Closed
-
MDEV-27510 Query returns wrong result when using split optimization
- Closed
I think we have the same problem with 10.5.21-MariaDB-1:10.5.21+maria~deb10-log on server with replication.
With split_materialized=on query returns correct results for 70 rows. 71+ rows returns correct result only for first row other rows returns null values for joins.
Example of result:
70 ids:
editionNames | editionsIds | p.id
rock oldies | 1 | 1
rock oldies | 1 | 2
indies | 2 | 3
71+ ids:
editionNames | editionsIds | p.id
rock oldies | 1 | 1
null | null | 2
null | null | 3
The ids are not the problem I tried to swap them.
Local version 10.5.17-MariaDB works fine but there is no replication. I will try to reproduce the problem locally with 10.5.21-MariaDB-1:10.5.21+maria~ubu2004-log.
Problem should not be caused by data, because it appeared right after upgrade from 10.3.x to 10.5.21.