[Info-Ingres] Lock escalation caused by bad page estimate

Hi Everyone,



I have a uniquely keyed btree table with 158pages. Ithas all the
defaullt fillfactors etc. I have freshly modified it, I have rebuilt the
stats on it.



Why does the optimiser think there are only 40 pages in it?



Sadly, because it doesn't think there are more than maxlocks (50) pages,
it goes into page reading and then has to escalate. Which is filling the
errlog with escalation messages.



Marty