diff options
| author | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-11-05 15:53:28 +0100 |
|---|---|---|
| committer | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-11-05 15:53:28 +0100 |
| commit | b1cf4dcd3c5da67511be6de3fa8ba19604758ed6 (patch) | |
| tree | 61c7646440805b1cc1792e0257e611e61c371156 /sql/ha_partition.cc | |
| parent | 5a897c8b4ee38e591c3955e848b5a0ba6b332fe8 (diff) | |
| download | mariadb-git-b1cf4dcd3c5da67511be6de3fa8ba19604758ed6.tar.gz | |
Bug#40494: MYSQL server crashes on range access with partitioning and
order by
Problem was that the first index read was unordered,
and the next was ordered, resulting in use of
uninitialized data.
Solution was to use the correct variable to see if
the 'next' call should be ordered or not.
Diffstat (limited to 'sql/ha_partition.cc')
| -rw-r--r-- | sql/ha_partition.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/ha_partition.cc b/sql/ha_partition.cc index 14e321218ca..303a2c152fb 100644 --- a/sql/ha_partition.cc +++ b/sql/ha_partition.cc @@ -4084,7 +4084,7 @@ int ha_partition::read_range_next() { DBUG_ENTER("ha_partition::read_range_next"); - if (m_ordered) + if (m_ordered_scan_ongoing) { DBUG_RETURN(handle_ordered_next(table->record[0], eq_range)); } |