MySQL Bugs: #31977: HIGH_PRIORITY and LOW_PRIORITY modifier don't look working properly.

Bug #31977	HIGH_PRIORITY and LOW_PRIORITY modifier don't look working properly.
Submitted:	31 Oct 2007 8:52	Modified:	29 Nov 2007 7:53
Reporter:	Mikiya Okuno	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S3 (Non-critical)
Version:	4.1, 5.0, 5.1	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	optimizer scheduler priority myisam

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

SHOW FULL PROCESSLIST output shows that write requests are processed before read requests with HIGH_PRIORITY modifies.

Attachment: show_full_processlist1.txt (text/plain), 15.76 KiB.

test case

Attachment: bug31977.test (application/octet-stream, text), 1.39 KiB.