| Bug #47213 | InnoDB mutex/rw_lock should be conscious about memory ordering other than Intel | ||
|---|---|---|---|
| Submitted: | 9 Sep 2009 9:46 | Modified: | 18 Jul 2014 9:20 |
| Reporter: | Yasufumi Kinoshita | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.0, 5.1.36 + plugin 1.0.3 | OS: | Linux (PowerPC SMP) |
| Assigned to: | Yasufumi Kinoshita | CPU Architecture: | ARM |
| Tags: | Contribution | ||
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
[9 Sep 2009 9:47]
Yasufumi Kinoshita
[20 Oct 2009 8:50]
Yasufumi Kinoshita
The new more stable patch for InnoDB Plugin 1.0.3
Attachment: innodb_1.0.3_sync_fix_for_ppc_smp_2.patch (text/x-diff), 9.13 KiB.
[20 Oct 2009 8:51]
Yasufumi Kinoshita
The new more stable patch for InnoDB Plugin 1.0.4
Attachment: innodb_1.0.4_sync_fix_for_ppc_smp_2.patch (text/x-diff), 8.65 KiB.
[12 May 2014 4:46]
Yasufumi Kinoshita
emperimental patch for 5.6
Attachment: memory_barrier_experimental_5.6_4.diff (text/x-patch), 9.24 KiB.
