> Safest thing for you is to use our latest 3.23 binaries which are
> statically linked with stable glibc and with some additional patches.
For this reason and greater simplicity :) I have been using your binaries
for a long time now. Part of the reason we never tested BDB tables...
> There can be another source of problems with REPLACE. As it has to
> DELETE a row first, it might take a lot of time on huge table if MySQL
> is not able for some reason to utilize index in order to locate rows.
Now this seems like it might be related. On a variable sized row table, this
could be a source of problems. As a note, there is a unique index it should
be using. Is there a way to see if it is, or USE INDEX like select?
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
