From: Dmitry Y. <fir...@ya...> - 2009-03-05 20:29:32
|
Bill et al, > CARDINALITY > PAGES Both values are available to the optimizer, they're just not surfaced. > Proposal - what do you all think about adding a new column to RDB$RELATIONS This sounds as a bad idea to me. I don't like any runtime "magic" fields in persistent system tables. Even if we speak about a real computed field, then it's going to be computed via some BLR anyway, so we could be publicly expose it as a built-in function. There's also another option. I expect v3.0 to have all its database statistics (i.e. GSTAT output) stored in the database itself and refreshed periodically. This is a separate subject which will be discussed later. But if this would be implemented, then we could surface all that stored statistics via a bunch of new monitoring tables. Dmitry |