DatabaseMessageIndex (the default) fails with 200k+ messages
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Nikerabbit
	Jun 16 2012, 8:19 AM

Description

It fails with packet size too long message. Could make it to do multiple inserts, or at least document the limitation.

Version: unspecified
Severity: trivial

• bzimport raised the priority of this task from to High.Nov 22 2014, 12:27 AM

• bzimport set Reference to bz37646.

• bzimport added a subscriber: Unknown Object (MLST).

If this is a database error, you can change my.cnf.

(In reply to comment #1)

If this is a database error, you can change my.cnf.

Should retry this with latest version, but yes we can document it until the proper fix (smaller inserts, split into multiple if needed) is done.

Is this still happening? Is this still high priority?

I haven't tested (I don't have wiki with so many messages handy). It will be a high priority one a wiki goes over the threshold.

Nikerabbit lowered the priority of this task from High to Low.Jan 26 2015, 9:20 PM

I believe this is resolved with recent refactoring to do replace + delete rather than delete_all + insert.