Derrek,
I don't know of any particular problem. You might try to alter the
composite index to cluster. I know you have dropped and re-created
the table, but the index could still be slanted depending on when it
was created and how the rows were loaded.
Other than that though, I'm at a loss. I especially don't understand
why the time varies so wildly between 1 second and an hour. Do any of
your onstat -p stats grow while the query is executing? (Bufwaits perhaps?)
--Craig (craig@chemistry.utah.edu)
}
} I've got a curious problem I'd be interested in hearing any thoughts on.
} The machine is an HP9000/755 with HP-UX 9.01 and OnLine 5.01.UD1. The problem
} is with a table that has several indexes, including 1 on field1 and 1 on
} (field1, field2, field3, field4) (obviously I'm making up the column names).
} The table has approx. 1.5 million rows and is 1 table out of 550 or so in its
} particular database. A query of the form:
}
} select * from table where field1="xxx"
}
} comes back within a second or so. A query like:
}
} select * from table where field1="xxx" and field2="yyy"
}
} takes between <1 second to over an hour (!), depending on the value of field1.
}
} [remainder of message deleted...]