Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a table with 1,000,000 records and I’m running a statement that’s deleting ~700k rows. The auto-increment-index is of course still at 1,000,001. The highest primary key afterwards for example 40,000.
After such a huge deletion of rows should I manually set the index back to 40,001 or optimize the table in any way? Or doesn’t MySQL care for this huge gap when inserting new rows and using the index in select statements afterwards (in terms of speed)?
The MySQL manual says:
But don’t reset the primary key, it can mess things up. The INT datatype (presumably) has a lot of room to grow from 1M.
In terms of query speed, it doesn’t matter whether the index value is at 1 000 000 or at 1 000 000 000.