MySQL Bugs: #46767: Crash using unknown column name in HAVING clause subquery with materialization

Bug #46767	Crash using unknown column name in HAVING clause subquery with materialization
Submitted:	17 Aug 2009 20:32	Modified:	24 Aug 2009 7:10
Reporter:	Patrick Crews	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Optimizer	Severity:	S3 (Non-critical)
Version:	5.4/6.0	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	assertion failed, crashing bug, materialization, subquery

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

full crash output with backtraces, etc

Attachment: bug46767_crash_output.txt (text/plain), 16.28 KiB.

Full MTR test case with original and simplified queries

Attachment: bug46767_test.txt (text/plain), 8.08 KiB.