[MDEV-28348] InnoDB spatial index is not optimal with ST_Intersects Created: 2022-04-19 Updated: 2023-04-14 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | GIS, Storage Engine - InnoDB |
| Affects Version/s: | 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8 |
| Fix Version/s: | 10.4, 10.5, 10.6, 10.11 |
| Type: | Bug | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Marko Mäkelä |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
The estimation of 4001 rows does not look good. In fact, no rows match the condition. |
| Comments |
| Comment by Alexander Barkov [ 2022-04-19 ] | ||||||||
|
Note, in version 10.2 to 10.5, the following trick with a table rebuild helps:
Now the output is much better. Starting from 10.6 the rebuild does not help. |