Re: summary of locks overflow

Scott Kolaya wrote: > > It doesn't sound like update stats, caused the overflow. It sounds like it > stopped it from happening. If the stats weren't updated the database > wouldn't use the indexes and would scan the table. This is especially bad > on a join with repeatable read isolation. The database might choose a hash > join in memory and lock all the rows in both tables. > > Scott Kolaya > DBA Fleet Services > That makes more sense. Thanks for the explanation. John Carlson Informix DBA WH Smith, Inc.