I am using MySQL V4.0.2alpha and I have set MAX_BINLOG_SIZE to 2M in order to
not have to run a CRON job or something similar to do a "FLUSH LOGS"
intermittently. This should cause the binary log file to be rotated after it
has reached 2M according to the documentation. This hasn't
g file reached
AS> the filesystem limit of 2GB (on ext2) all updates written to the file
AS> are lost and the replication stops without any error message.
AS> The strange thing is that we set the max_binlog_size variable in the
AS> my.cnf file to a limit of 30MB. The variable will be ig
message.
The strange thing is that we set the max_binlog_size variable in the
my.cnf file to a limit of 30MB. The variable will be ignored if we use
the new procedure to rotate the binlog files but works fine with the old
one.
The final result now is that the DBs are out of sync and we have to
spend
message.
The strange thing is that we set the max_binlog_size variable in the
my.cnf file to a limit of 30MB. The variable will be ignored if we use
the new procedure to rotate the binlog files but works fine with the old
one.
The final result now is that the DBs are out of sync and we have to
spend
