Bug #20232 MERGE table corruption error message should indicate which member is corrupted
| Submitted: | 2 Jun 2006 15:51 | Modified: | 5 Jul 2006 22:05 |
|---|---|---|---|
| Reporter: | [ name withheld ] | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Merge storage engine | Severity: | S4 (Feature request) |
| Version: | 4.1.18 | OS: | Linux (RedHat 9) |
| Assigned to: | CPU Architecture: | Any |
[2 Jun 2006 15:51]
[ name withheld ]
[3 Jun 2006 13:30]
Valeriy Kravchuk
Thank you for a reasonable feature request.
[5 Jul 2006 22:05]
[ name withheld ]
Is it possible that this can be changed from a feature request to a bug and be assigned? That the server doesn't provide adequate information to troubleshoot in this case seems a fair reason to be classified as a bug rather than a feature request. This is a huge time waste for your users using large merge tables. We had a similar instance today on a different merge table of ours and we spent almost 3 hours trying to determine which of the dozens of member tables in our merge was the one creating the problem. Being able to dramatically reduce the time to recover when a member table of a merge fails would be a significant improvement for your merge table users. Thanks, Tabor
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.