gray_area_2 wrote:

>
> Is here a way to avoid this TIP growth? I have tried to reopen
> connection, doesn't help.

Transactions that rolled back may have left changes in the database -
changes that should not be seen by other transactions and should be
garbage collected. Restarting the server doesn't get rid of those
changes. A sweep does, and in theory, with some work we could
recognize when a TIP is completely committed and release it. However,
the current mechanism for finding the appropriate TIP for a transaction
depends on the sequence. Sure, we could fake it, but the saving is
relatively small (in the cases we've thought about) and the damage
that a bug could do in that area is huge (consider applying the states
from the wrong page - committed records would disappear, rolled back
records would reappear) and the changes of a bug are above zero
(consider the read-only problem).

Maybe you've got a case where a 2 bit per transaction growth is
critical?


Regards,


Ann