Bug #3357 If the statement is long, the error message is trunc and important info is lost
Submitted: 1 Apr 2004 6:25 Modified: 4 May 2004 16:05
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[1 Apr 2004 6:25] Guilhem Bichot
If your slave gets an error, for example a query
UPDATE <very long query, kilobytes>
got a different error code on slave and master,
then in SHOW SLAVE STATUS and in the .err you get a truncated message of 1024 bytes like:
Slave: Query 'UPDATE <truncated>, error_code=0.
It's not a problem to lose the end of the query, because the slave tells you at which position in the binlog and relay log it stopped so you can always do mysqlbinlog to see the exact query.
But it's a problem that we lose the important information which was after the query: the text explaining that
"got different errors on master and slave: error on master %d error on slave %d".

How to repeat:
see description

Suggested fix:
I should rephrase the error sentence so that the query goes last.
[4 May 2004 16:05] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Fixed in ChangeSet@1.1793.1.1, 2004-05-04 15:48:40+02:00, guilhem@mysql.com