MySQL Bugs: #104889: The table '../tmp/#sql…' is full error causes developers confusion

Bug #104889	The table '../tmp/#sql…' is full error causes developers confusion
Submitted:	9 Sep 2021 12:53	Modified:	9 Sep 2021 13:37
Reporter:	Simon Mudd (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Logging	Severity:	S3 (Non-critical)
Version:	8.0.26	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This error has caused quite a few developer I know a lot of confusion.
Why is it full? What can I do about it? None of that is clearly indicated.

It would be better to provide a pointer to innodb_temp_data_file_path setting which might be configured something like:

innodb_temp_data_file_path=ibtmp1:12M:autoextend:max:10G

This would allow the developer to look up the configuration setting and modify it if required.

How to repeat:
Generate implicit temporary tables larger than the configured size.

Suggested fix:
A preliminary patch is offered here: https://github.com/mysql/mysql-server/pull/368.  Is it good enough to accept?

The 2 issues not handled are translating the error message into multiple languages and the adjustment of the test cases.

Please clarify if the PR is enough or you need one or both of these issues resolved.

Hello Simon,

Thank you for the report and feedback.
Verifying as an enhancement request for the meaningful error message in the given context. Thank you!

regards,
Umesh

Ideally, this configuration should be removed. It is only used for temporary tablespace undo logs.

Temporary table undo should go to dedicated Tablespaces. Should be truncated like other undo Tablespaces.