Comments - MariaDB 64bit eats virtual memory
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Thanks a lot for your answer. By the time I've analysed the issue a little bit and can reproduce the error.
The issue pop up if I run a SELECT Statement with one single FUNCTION:
SELECT tbl_tmp_import_deals_etl1.counterparty_id, tbl_tmp_import_deals_etl1.deal_id_kits AS `deal_id`, GET_SUB_PORTFOLIO(tbl_tmp_import_deals_etl1.deal_id) AS `sub_portfolio`, @v_run_id FROM tbl_tmp_import_deals_etl1;
Where the function is specified as:
CREATE FUNCTION test.`GET_SUB_PORTFOLIO`(v_deal_id BIGINT(20)) RETURNS varchar(50) READS SQL DATA DETERMINISTIC BEGIN
DECLARE r_rueck VARCHAR(50);
SELECT IFNULL(value,'no subportfolio') FROM tbl_tmp_import_deal_type_detail WHERE deal_id = v_deal_id INTO r_rueck;
RETURN r_rueck; END;
Alle other functions (arround 30) running through without any trouble. Database has a size of round about 5GB.
EXPLAIN SELECT reported: type: ref select_type: simple possible_key: index_1 key: index_1 key_len: 9 ref: const
Any idea?
Thank you very much and have a nice weekend Andreas