diff options
| author | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-12-28 12:33:49 +0100 |
|---|---|---|
| committer | Mattias Jonsson <mattias.jonsson@sun.com> | 2008-12-28 12:33:49 +0100 |
| commit | f257aac8148626c81fb3447eeb2bb85d9756735e (patch) | |
| tree | 3dfd473d32b5ff19a5d5d6ea94d513f5ceb9514b /libmysql | |
| parent | bcfa0cedb26c372ed978d54d8f3d785d616132fa (diff) | |
| download | mariadb-git-f257aac8148626c81fb3447eeb2bb85d9756735e.tar.gz | |
Bug#40972: some sql execution lead the whole databse crashing
Problem was an errornous date that lead to end partition
was before the start, leading to a crash.
Solution was to check greater or equal instead of only
equal between start and end partition.
NOTE: partitioning pruning handles incorrect dates
differently than index lookup, which can give different
results in a partitioned table versus a non partitioned
table for queries having 'bad' dates in the where clause.
mysql-test/r/partition_pruning.result:
Bug#40972: some sql execution lead the whole databse crashing
Updated result file
mysql-test/t/partition_pruning.test:
Bug#40972: some sql execution lead the whole databse crashing
Added test.
sql/sql_partition.cc:
Bug#40972: some sql execution lead the whole databse crashing
There can be cases where the start/cur partition is greater
than the end partition, so it must not continue, since that
can lead to a crash.
Diffstat (limited to 'libmysql')
0 files changed, 0 insertions, 0 deletions