Not if all those 6517 transactions are read-only, but for each update,
insert (or delete?) the transactions have done, duplicates of all
changed/inserted records are created due to the changes being visible for
only some of the transactions. And this affects the performance of the
database. Hence, it is a good idea to ascertain that the oldest transaction
is moving on.

Set

At 09:36 12.06.2003 +0000, you wrote:

>If the difference between oldest active and next transaction is
>increasing, will it effect the performance of the database (for sql
>query)?
>
>eg.
>Oldest Transaction 2248862
>Oldest Active 2248868
>Oldest snapshot 2248868
>Next transaction 2255385
>
>diff = 6517
>
>rgds, chooi-ting