[Tickets #12476] Re: Database running mad after update to 5.1.1

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12476
------------------------------------------------------------------------------
  Ticket             | 12476
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Database running mad after update to 5.1.1
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.1.1
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-07-19 16:46) wrote:

Since my history data set, even on production is not anywhere near as  
large as your data set, can you see if adding the following index  
improves this for you? EXPLAIN now shows that it is using the index so  
it should improve...

ALTER TABLE horde_histories ADD INDEX (history_modseq, object_uid);


If not, the next attempt would be to use something like:

  SELECT history_modseq FROM horde_histories WHERE object_uid LIKE  
'turba:%' ORDER BY history_modseq DESC LIMIT 1;

but I'd be wary of doing this since I doubt it would perform the same  
from one RDBMS to another.