Bug #3214 mysqlbinlog --read-from-remote-server --position prints wrong positions

Submitted: 17 Mar 2004 16:19 Modified: 20 Mar 2004 7:44
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[17 Mar 2004 16:19] Guilhem Bichot
Description:
[guilhem@gbichot2 client]$ /m/mysql-4.0/client/mysqlbinlog -j16841 /m/data/41/1/gbichot2-bin.000001 |head -n3
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
# at 16841
#040316 20:33:16 server id 1  log_pos 16841     Query   thread_id=5     exec_time=0     error_code=0

/*!40019 SET @@session.max_insert_delayed_threads=0*/;
# at 0
#700101  2:00:00 server id 1  log_pos 0         Rotate to gbichot2-bin.000001  pos: 16841
# at 4
#040316 20:33:16 server id 1  log_pos 16841     Query   thread_id=5     exec_time=0     error_code=0

The "at 4" above should be "at 16841"

How to repeat:
see description

Suggested fix:
will fix this (have a patch).
[20 Mar 2004 7:44] 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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fixed in 4.1 in ChangeSet@1.1704, 2004-03-18 20:53:33+02:00, guilhem@mysql.com

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.049 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.