WordPress.org

1. vickie
   Member
   Posted 1 year ago #

   Really grateful if anyone can help as my site is running REALLY slowly (just added W3 Total Cache plugin which has patched it up for a bit but not fixed the problem)

   I checked the PHP d/base and have the following error:

   "Problems with indexes of table wp_comments More than one INDEX key was created for column comment_approved More than one INDEX key was created for column comment_post_ID"

   http://www.WhatsinWapping.co.uk

2. malevola
   Member
   Posted 1 year ago #

   Are you getting something that looks like this when you look at the structure of the "Table: wp_comments"?
   `Indexes:

   Keyname	 	 	 	 	 Type	 Cardinality	 Field
   PRIMARY					PRIMARY	 0 		comment_ID
   comment_post_ID				INDEX	 None 		comment_post_ID
   comment_approved_date_gmt		INDEX	 None 		comment_approved
   	 	 	 	 	 	 	 	comment_date_gmt
   comment_date_gmt	 	 	INDEX	 None 		comment_date_gmt
   comment_parent	 	 	 	INDEX	 None 		comment_parent
   comment_approved	 	 	INDEX	 None 		comment_approved

   More than one INDEX key was created for column comment_approved

   Notice how in the field column shows two instances of the field comment_approved? Unless you have have duplicate or repeated keynames (usually with _2 or _3 after the name), then everything is working as it should. You can ignore the warning completely.

3. vickie
   Member
   Posted 1 year ago #

   Hi malevola

   Thanks for getting back on this and sorry only just saw your reply

   I did have duplicated keynames (with _2 after them like you say). I did manage to speak to a DBA at work and we dropped the duplicate indexes.

   This was causing me problems when I tried to restore a database backup as it said that there were duplicate records ...removing the duplicate indexes has fixed the problem.

   They weren't familiar with WordPress databases by the way (but very experienced DBA) so please feel free to add to this as it's quite a tricky one for us beginners!

   Thanks again

Topic Closed

This topic has been closed to new replies.