[MDEV-30282] Uncontrollable memory consumption upon GROUP_CONCAT with ORDER BY Created: 2022-12-20  Updated: 2023-06-17  Resolved: 2023-06-17

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-9531 GROUP_CONCAT with ORDER BY inside tak... Closed

 Description   

Grows to 70G and dies on my machine, at least on 10.6 (10.6.9 and 10.6.11)

49fb1f02745edc82bcffc83f7e4d3bf0309a73af

perl /mnt8t/src/rqg/run.pl --gendata=conf/zz/full_text_search.zz --nometadata --scenario=Standard --ps-protocol --filter=conf/ff/need-reconnect.ff  --queries=1000000 --gendata=advanced --reporters=Backtrace,ErrorLog,Deadlock,MemoryUsage,FeatureUsage --mysqld=--slave-transaction-retry-errors="1213,1205" --mysqld=--secure-timestamp=NO --mysqld=--table-open-cache-instances=64 --mysqld=--log-output=FILE,TABLE --threads=4 --duration=400 --mysqld=--max-statement-time=300 --mysqld=--lock-wait-timeout=300 --mysqld=--innodb-lock-wait-timeout=300 --views --grammar=conf/yy/optimizer.yy --gendata=simple --mysqld=--innodb-compression-algorithm=none --base-port=14000 --server1-basedir=/data/releases/10.6.9-5 --vardir=/home/elenst/logs/var3 --seed=1671514559



 Comments   
Comment by Elena Stepanova [ 2023-06-17 ]

The troublesome queries in the stress test were doing GROUP_CONCAT with ORDER BY from a large join.
Thus it is a duplicate of MDEV-9531, where the chosen solution was to use max_session_mem_used when needed.

Generated at Thu Feb 08 10:15:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.