On Jun 19, 2004, at 6:03 AM, Terry Riley wrote:
Just a suggestion, Kevin, but how about changing from INT to BIGINT?
I thought of trying that, but since we're nowhere near the limit even for an INT I think changing to BIGINT is premature. I want to find out a bit more about what's happening first. The fact that it stops at such a low number makes me think it's not related to the size of the field.
I saw a reference in a post (to a different mailing llist) to a tables auto_increment limit, as though that was something different from the max value of an INT, but I haven't run across it in any official documentation.
Kevin
----------Original Message---------
We have a table with a primary index which is INT NOT NULL AUTO_INCREMENT.
After inserting ~87,000,000 entries, we started seeing error 1062, ER_DUP_ENTRY.
We can get going again after doing an ALTER TABLE to reset the auto_increment starting point, but this takes about an hour...
I've seen a couple of places where how to get around this problem was discussed, but nobody seems to discuss *why* this occurs in the first place.
Does anyone know why MySQL would start failing to increment an
auto_increment index properly when it's nowhere near the upper limit?
Does anyone know a way to get things functioning again without a couple
of hours downtime?
Hoping there's an answer out there somewhere...
Kevin Brock [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
