6.0.0-beta13
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
4/11/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#12476] Database running mad after update to 5.1.1
*
Your Email Address
*
Spam protection
Enter the letters below:
. . __.\ /\ / | | (__ >< >< |___|___.__)/ \/ \
Comment
> 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.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers