> Long running read committed read-only transactions aren't a problem at
> all. If you are using Firebird 2.5, I wonder what the Trace API returns
> in respect to transaction tracing.
>

Ok, so i will start to think about transaction pool (only for read only
red commited transaction)

Can you confirm

if a read only transaction (isc_tpb_read + isc_tpb_read_committed +
isc_tpb_rec_version)
die without any commit or rollback (network
error, application bug, etc.) then it's no matter for the firebird server ?

Also what a time aleave i need to setup for each transaction before to
commit them? 30 s ? 1 min ? 10 min ? more ?

Thanks by advance


[Non-text portions of this message have been removed]