> -Original Message-
> From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 28, 2005 06:30
> To: mysql@lists.mysql.com
> Subject: Re: Weird database files
>
>
> Hello.
>
> > On the master we're still running 4.0.16, the s
Hello.
> On the master we're still running 4.0.16, the slaves are up to 4.1.13.
If you can - upgrade the master server.
Jeff McKeon wrote:
>>Jeff wrote:
>>
>>>Had problem with our database this weekend, apparently an
>>
>>app did an
>>
>>>insert query that was huge size wise and t
> Jeff wrote:
> > Had problem with our database this weekend, apparently an
> app did an
> > insert query that was huge size wise and this totally boogered up
> > replication downstream. Also I cant read past that point in the
> > binlog using mysqlbinlog on the master server. It complains that:
> Jeff wrote:
> > Had problem with our database this weekend, apparently an
> app did an
> > insert query that was huge size wise and this totally boogered up
> > replication downstream. Also I cant read past that point in the
> > binlog using mysqlbinlog on the master server. It complains th
Hello.
Yes, these files are from some unterminated query. See:
http://dev.mysql.com/doc/mysql/en/temporary-files.html
You may want to use --start-position (--start-datetime) and
--stop-position (--stop-datetime) to skip the problematic statement
and perform necessary updates on the sla
Had problem with our database this weekend, apparently an app did an
insert query that was huge size wise and this totally boogered up
replication downstream. Also I cant read past that point in the binlog
using mysqlbinlog on the master server. It complains that:
ERROR: Error in Log_event::rea
