Issue Bug Closed

#20065MYSQL Replication breaks because of lack of AUTO_INCREMENT PK in cache_pagesection

Lukas Taferner 02/20/09, 19:54 updated 08/06/10, 13:21

Description

Hi,

recently I discovered that in a high load environment with multiple replicating MYSQL hosts the replication tends to break beacuase of lack of an auto incrementing primary key in the table cache_pagesection.

Here is my solution:

ALTER TABLE cache_pagesection DROP PRIMARY KEY;
CREATE TABLE cache_pagesection (
uid int(11) NOT NULL auto_increment PRIMARY KEY,
KEY pageid_mphash (page_id,mpvar_hash),
PRIMARY KEY,
);

Tho only problem seems to be a limitaiton of the SQL compare script, which is unable to handle PK Changes.

best regards,

Lukas Taferner

(issue imported from #M10508)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.