Dave,
please post the first errors in the .err log. I want to know what the
original problem was. The error below probably comes from that you have set
innodb_force_recovery=SRV_FORCE_NO_LOG_REDO
Note that Red Hat kernels 2.4.18 are suspected to cause file corruption
easily.
Best regards,
Heikk
Tomas,
did you use rsync to copy the ibdata file of a RUNNING mysqld server?
http://dev.mysql.com/doc/mysql/en/Backing_up.html
Both MyISAM and InnoDB cache their data in memory while mysqld is running.
The ibdata files, ib_logfiles, .MYI, .MYD files are not up to date in the
file system. Your bac
Hi,
does InnoDB guarantee that the values of an autoincrement column do always
increase?
What happened to me is that a select * from my_table returns something like
id | ...
10
11
5
12
13
where id is defined as int(10) unsigned NOT NULL auto_increment
and is the primary key of the ta
I am aware of that.
But from my experience MySQL returns the the rows in the order that you
inserted them.
Assuming this is the case, I was wondering if the result I have seen means
that the order of autoincrement values does not correspond to the order in
which inserts are done.
Frank
On Mon
hello everybody,
I used myisamchk /path/to/datadir/mysql/*.* to find memory already in
use and free memory available for all tables in 'mysql' database.where mysql in
above path refers to mysql database.
I got two types of errors for all tables in that directory.
They are
myisamchk:e
The ANALYZE TABLE entry in the manual doesn't say anything about
performance optimization.
How do I get optimum performance out of ANALYZE TABLE?
Can I just set the same variables as I would with REPAIR TABLE?
key_buffer_size
sort_buffer_size
myisam_sort_buffer_size
Also... Does A.T. always need to
