MYSQL Replication breaks because of lack of AUTO_INCREMENT PK in cache_treesection
Thank you for implementing auto_incrementing PK's in cache_pages and cache_pagesection in 4.3, the table cache_treelist however still has a md5 hash as primary key. This will break replication in a multimaster mysql setup.
CREATE TABLE `cache_pages` (
`id` int(11) unsigned NOT NULL auto_increment,
PRIMARY KEY (`id`)
(issue imported from #M11184)
Updated by Lukas Taferner about 12 years ago
Hi Oliver, we have a setup with multiple MySQL Masters with crossreplication i.e. every write operation is replicated to all the other DB hosts. We could have chosen to set caching to 5 min. and exclude cache* from replication, but it's better to be able to clear the cache on the livebackend (and replicate this to the other hosts) in realtime.
Updated by Chris topher over 8 years ago
- Status changed from Needs Feedback to New
Alexander Opitz wrote:
does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Table "cache_treesection" does not exist anymore in current versions.
The problem however is still present for the table "cache_imagesizes".