Giulio Ferro wrote:
Paul J Stevens wrote:
That don't smell right. At all!
2360882 rows is totally fucked. That query shouldn't have to scan more
than two or three rows. Your indexes are possibly messed up. The
physmessage_id_index isn't being used at all, afaict.
try:
show create table dbmail_messageblks;
maybe that will tell us something.
Mmh, I've used the standard sql files to create the dbmail db
mysql> show create table dbmail_messageblks;
+--------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create
Table
|
+--------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| dbmail_messageblks | CREATE TABLE `dbmail_messageblks` (
`messageblk_idnr` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`physmessage_id` bigint(20) unsigned NOT NULL DEFAULT '0',
`messageblk` longblob NOT NULL,
`blocksize` bigint(20) unsigned NOT NULL DEFAULT '0',
`is_header` tinyint(3) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (`messageblk_idnr`),
KEY `physmessage_id_index` (`physmessage_id`),
KEY `physmessage_id_is_header_index` (`physmessage_id`,`is_header`),
CONSTRAINT `dbmail_messageblks_ibfk_1` FOREIGN KEY (`physmessage_id`)
REFERENCES `dbmail_physmessage` (`id`) ON DELETE CASCADE ON UPDATE
CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=747417 DEFAULT CHARSET=utf8 |
+--------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.06 sec)
If you explain to me what this table do and point me in the right direction,
I can try and write a script to correct the messed up data, if you deem
it possible.
I'm looking for any solution short of creating a new db and importing
the boxes
with imapsyc, given how bad this utility works...
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
