Subject | Re: GSTAT / Transactions question |
---|---|
Author | Alexander V.Nevsky |
Post date | 2004-04-30T14:01:43Z |
--- In firebird-support@yahoogroups.com, "nico_callewaert@p..."
<ncw@p...> wrote:
reconnect to the application again, then it seems the Transaction are
released :
the database ?? Or am I misinterpreting the GStat output ?
Nico, "The oldest active transaction is
not the oldest transaction currently running. Nor is it the oldest
transaction marked Active in the TIP. (Alas). It is the oldest
transaction
that was active when the oldest transaction currently active started.
The bookkeeping on this is hairy, and I frankly don't remember how it
was done, but that's the rule, and it does work." Surely this great
aricle by Ann Harrison is placed somewhere on www.ibphoenix.com, but I
this time pasted this fragment from file I saved long ago being afraid
I can forget link or link will be chaged. When you disconnected there
was not active transactions to force header update. When you started
transaction it was performed.
Best regards,
Alexander.
<ncw@p...> wrote:
> Hi,application, this is the GStat output :
>
> There is something I don't understand. When I connect to my
>25179, even after a hard Commit ?? The strangest thing is, when I
> Oldest Active: 25176
> Next Transaction: 25177
>
> After I opened 1 form in the application, this is the next GStat :
>
> Oldest Active: 25176
> Next Transaction: 25179
>
> Until here, no problem.
> But when I disconnect from the apllication, GStat remains 25176 /
reconnect to the application again, then it seems the Transaction are
released :
>transaction would be finished or at least after I disconnected from
> Oldest Active: 25178
> Next Transaction: 25179
>
> I don't get it at all, I was expecting after a hard Commit that the
the database ?? Or am I misinterpreting the GStat output ?
Nico, "The oldest active transaction is
not the oldest transaction currently running. Nor is it the oldest
transaction marked Active in the TIP. (Alas). It is the oldest
transaction
that was active when the oldest transaction currently active started.
The bookkeeping on this is hairy, and I frankly don't remember how it
was done, but that's the rule, and it does work." Surely this great
aricle by Ann Harrison is placed somewhere on www.ibphoenix.com, but I
this time pasted this fragment from file I saved long ago being afraid
I can forget link or link will be chaged. When you disconnected there
was not active transactions to force header update. When you started
transaction it was performed.
Best regards,
Alexander.