Re: Transaction (was: Re: [Dbi-interbase-devel] Re: fixing InterBase.pm and IBPerl.pm for transactions)

[Mark D. A. <md...@di...>]

> i don't know enough about how the interbase engine works to know what would
> show it, but this behavior certainly *should* cause starvation.
> the semantics of retaining is that the client connection retains locks on objects
> involved in the committed transaction. so if every commit retains locks, the client
> will gradually accumulate more and more locks, for as long as it lives.
> this will eventually cause either lock timeouts or deadlock, assuming that reasonable
> isolation levels are chosen.

i should add -- that is, if there is more than one connection trying to perform writes.
if only one connection is doing writes, this should work -- again, assuming
appropriate transaction parameters are set by all connections so they can choose
what isolation to use (i.e. so the readonly connections will see committed changes
even though another is known to be pending).

-mda