Doug McNaught wrote:
> Randolf Richardson <rr@8x.ca> writes:
>
>
>> What about adding a "total number of rows" value to the internal
>>header of each table which gets incremented/decremented after each row is
>>INSERT/DELETE has been committed. This way, a generic "count(*)" by itself
>>could simply return this value without any delay at all.
>
>
> Because different sessions have a (validly) different concept of what
> that number should be, due to MVCC.
The count(*) information can be revisioned too, am I wrong ? I'm able to
create a trigger that store the count(*) information in a special table,
why not implement the same in a way "builded in" ?
Regards
Gaetano Mendola