Subject | Next transaction /only/ increments |
---|---|
Author | smartsbroadcast |
Post date | 2007-11-17T19:52:29Z |
The platform is Fedora Core 5 hosting Firebird/SuperServer 2.0.3
(LI-V2.0.3.12981 Firebird 2.0) using the binary tarsball as downloaded
from firebirdsql.org. The client application is a simple Perl test
script using DBI-1.601 and DBD::InterBase 0.47, the current latest
versions of each. I'm using the Firebird-supplied ``employee.fdb''
database for this simple test.
The crux of the question is that ONLY the ``Next transaction'' value
increments. All of the other transaction-related counters reported by
``gstat -h'' remain static. The application is such that ``Next
transaction'' increments at the rate of once per second. I am aware of
the importance of ``keeping the OIT moving'' and am curious if ONLY
the incrementing of ``Next transaction'' is a problem waiting to happen.
If need be, I can post the short Perl script here (but am aware that
this is not the venue for DBI and DBD queries). So I have framed the
question in a general Firebird context concerning the transaction
counters.
(LI-V2.0.3.12981 Firebird 2.0) using the binary tarsball as downloaded
from firebirdsql.org. The client application is a simple Perl test
script using DBI-1.601 and DBD::InterBase 0.47, the current latest
versions of each. I'm using the Firebird-supplied ``employee.fdb''
database for this simple test.
The crux of the question is that ONLY the ``Next transaction'' value
increments. All of the other transaction-related counters reported by
``gstat -h'' remain static. The application is such that ``Next
transaction'' increments at the rate of once per second. I am aware of
the importance of ``keeping the OIT moving'' and am curious if ONLY
the incrementing of ``Next transaction'' is a problem waiting to happen.
If need be, I can post the short Perl script here (but am aware that
this is not the venue for DBI and DBD queries). So I have framed the
question in a general Firebird context concerning the transaction
counters.