delta/mariadb-git.git/sql/select_handler.cc, branch 10.56-MDEV-30986

Added detection of memory overwrite with multi_malloc

2023-02-27T17:25:44+00:00

This patch also fixes some bugs detected by valgrind after this
patch:

- Not enough copy_func elements was allocated by Create_tmp_table() which
  causes an memory overwrite in Create_tmp_table::add_fields()
  I added an ASSERT() to be able to detect this also without valgrind.
  The bug was that TMP_TABLE_PARAM::copy_fields was not correctly set
  when calling create_tmp_table().
- Aria::empty_bits is not allocated if there is no varchar/char/blob
  fields in the table.  Fixed code to take this into account.
  This cannot cause any issues as this is just a memory access
  into other Aria memory and the content of the memory would not be used.
- Aria::last_key_buff was not allocated big enough. This may have caused
  issues with rtrees and ma_extra(HA_EXTRA_REMEMBER_POS) as they
  would use the same memory area.
- Aria and MyISAM didn't take extended key parts into account, which
  caused problems when copying rec_per_key from engine to sql level.
- Mark asan builds with 'asan' in version strihng to detect these in
  not_valgrind_build.inc.
  This is needed to not have main.sp-no-valgrind fail with asan.

MDEV-23825 Join select_handler and Pushdown_select + XPand changes

2020-09-27T06:30:23+00:00

Merge 10.4 into 10.5

2020-03-27T07:39:15+00:00

MDEV-21887: federatedx crashes on SELECT ... INTO query in select_handler code

2020-03-26T12:01:44+00:00

Backport to 10.4:

- Don't try to push down SELECTs that have a side effect

- In case the storage engine did support pushdown of SELECT with an INTO
  clause, write the rows we've got from it into select->join->result,
  and not thd->protocol.  This way, SELECT ... INTO ... FROM
  smart_engine_table will put the result into where instructed, and
  NOT send it to the client.

MDEV-21887: federatedx crashes on SELECT ... INTO query in select_handler code

2020-03-06T22:14:41+00:00

- Don't try to push down SELECTs that have a side effect

- In case the storage engine did support pushdown of SELECT with an INTO
  clause, write the rows we've got from it into select->join->result,
  and not thd->protocol.  This way, SELECT ... INTO ... FROM
  smart_engine_table will put the result into where instructed, and
  NOT send it to the client.

MDEV-18553: MDEV-16327 pre-requisits part 3: move kill check in one place

2019-10-13T07:40:41+00:00

Kill check moved from send_data() methids in its wrapper:
send_data_with_check().

MDEV-19831 find_select_handler() now tries its best to find a

2019-08-24T17:49:15+00:00

handlerton that is able to processes the whole query. For that it
traverses tables from subqueries.

Select_handler now cleans up temporary table structures on dctor call.

MDEV-17096 Pushdown of simple derived tables to storage engines

2019-02-13T06:56:24+00:00

MDEV-17631 select_handler for a full query pushdown

Added comments and file headers for files introduced in these tasks.

MDEV-17096 Pushdown of simple derived tables to storage engines

2019-02-10T06:54:26+00:00

Resolved the problem of forming a proper query string for FEDERATEDX.
Added test cases.

Cleanup of extra spaces.

MDEV-17096 Pushdown of simple derived tables to storage engines

2019-02-07T01:02:44+00:00

MDEV-17631 select_handler for a full query pushdown

Interfaces + Proof of Concept for federatedx with test cases.

The interfaces have been developed for integration of ColumnStore engine.