RE: Re[6]: [Firebird-devel] Max transaction duration

[Claudio V. C. <cv...@us...>]

> -----Original Message-----
> From: fir...@li...
> [mailto:fir...@li...]On Behalf Of Pavel
> Cisar
> >
> > I believe that client death does establish an OIT.
>
> But when client dies and server notice, server performs the rollback,
> don't he ? If undo log is used on rollback to rewind changes and allow to
> mark transaction as committed instead, client or network failure should
> not affect OIT in most cases (every time undo log is used).

I don't know why this can't happen. If the client crashed, the server knows
the changes that it received until the client crashed. So, naively, I would
expect that the undo log is usable. Can you explain why not, Ann?


>
> But I meant read-only (by definition in trn parameter block) read
> committed transactions you mentioned earlier. They internally acquire pre-
> committed status, don't they ?

A small change was done on this, since there was a comment in the code,
inviting to do the change.

Pre-committed from the point of view of OAT management maybe, but I would
dare to call pre-committed only the system transaction.
;-)

And of course, there are some system tables whose changes are seen
immediately by every txn, regardless of its isolation level.

C.