Re: count(*) using index scan in "query often, update rarely" environment

On 10/7/05, Cestmir Hybl <cestmirl(at)freeside(dot)sk> wrote:
>
> Isn't it possible (and reasonable) for these environments to keep track of
> whether there is a transaction in progress with update to given table and if
> not, use an index scan (count(*) where) or cached value (count(*)) to
> perform this kind of query?
>

if i understand your problem correctly, then simple usage of triggers will
do the job just fine.

hubert