diff options
| author | Sergei Petrunia <psergey@askmonty.org> | 2017-02-14 07:18:55 -0800 |
|---|---|---|
| committer | Sergei Petrunia <psergey@askmonty.org> | 2017-02-15 13:47:41 -0800 |
| commit | e688d8144411e38253b7ec4e13f67a989da8bb76 (patch) | |
| tree | 5ba30789f77034c016ed45485d5cbf727e84defd /sql/gcalc_slicescan.h | |
| parent | 24911cee4e3be988848f6eab4d768849709f5256 (diff) | |
| download | mariadb-git-e688d8144411e38253b7ec4e13f67a989da8bb76.tar.gz | |
MDEV-10694 - SIGFPE and/or huge memory allocation in maria_create ...
The issue was that JOIN::rollup_write_data() used
JOIN::tmp_table_param::[start_]recinfo, which had uninitialized data.
These fields have uninitialized data, because JOIN::tmp_table_param
currently only stores some grouping-related data fields. The data about
the work (temporary) tables themselves is stored in
join->join_tab[...].tmp_table_param.
The fix is to make JOIN::rollup_write_data follow this convention
and look at the right TMP_TABLE_PARAM object
Diffstat (limited to 'sql/gcalc_slicescan.h')
0 files changed, 0 insertions, 0 deletions