[EMAIL PROTECTED]
www.nisc.coop
> -Original Message-
> From: Dan Buettner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 28, 2006 15:47
> To: Dirk Bremer
> Cc: mysql@lists.mysql.com
> Subject: Re: Relay-bin logs
>
> My bad, Dirk, sorry. I missed that you were
: Dirk Bremer
> Sent: Wednesday, June 28, 2006 15:59
> To: 'Dan Buettner'
> Cc: mysql@lists.mysql.com
> Subject: RE: Relay-bin logs
>
> Dan,
>
> Yes they are on the master. The master is not configured as a slave:
>
> mysql> show slave status;
>
5:23
> To: Dirk Bremer
> Cc: mysql@lists.mysql.com
> Subject: Re: Relay-bin logs
>
> Those do indeed have something to do with replication - they're a
> record of all data manipulation commands (inserts, updates, deletes,
> table creates and alters, etc). The slaves basicall
nisc.coop
> -Original Message-
> From: Dan Buettner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 28, 2006 15:23
> To: Dirk Bremer
> Cc: mysql@lists.mysql.com
> Subject: Re: Relay-bin logs
>
> Those do indeed have something to do with replication - they're a
>
Those do indeed have something to do with replication - they're a
record of all data manipulation commands (inserts, updates, deletes,
table creates and alters, etc). The slaves basically read the
commands from those files in order to replicate what the master has
done.
You can purge them fairly
I'm using MySQL 4.1 and the master runs on a Windows 2000 server. This
master replicates to several slaves.
While browsing the data directory on the master, there are a lot of
binary log files that are named:
MasterName-relay-bin.99 (where MasterName is the server-name and
99 is a six-dig
