Subject | Re: isc_start_transaction following isc_attach_database creates bad "trans leak" |
---|---|
Author | johan_bosaeus |
Post date | 2008-10-27T14:47:53Z |
--- In firebird-support@yahoogroups.com, "johan_bosaeus" <
OK. I have found it. I must set this option "isc_dpb_dbkey_scope" to
1 at all. "dbkey" obviously refers to the internal primary key, which
I don't use... And I found a little warning which exactly voices my
problem:
"
You can change the default duration of db_key values at connection
time by using the API or IBO. You can specify that the values must be
kept along the entire session; this means across the time elapsed
between the time you connect to the db and the time you disconnect.
However, keep in mind that this means garbage collection is stuck for
all this time. Internally, IB keeps a transaction open that stops
garbage collection. In highly interactive environments, this may
result in your database file growing at a big rate and the operations
in the database being each time slower. As a corollary, having an
auto-commit transaction working for all the day or using only
CommitRetaining or simply opening a transaction that's not committed
for several hours without need is not a wise solution.
"
YES INDEED!
Regards,
Johan
OK. I have found it. I must set this option "isc_dpb_dbkey_scope" to
1 at all. "dbkey" obviously refers to the internal primary key, which
I don't use... And I found a little warning which exactly voices my
problem:
"
You can change the default duration of db_key values at connection
time by using the API or IBO. You can specify that the values must be
kept along the entire session; this means across the time elapsed
between the time you connect to the db and the time you disconnect.
However, keep in mind that this means garbage collection is stuck for
all this time. Internally, IB keeps a transaction open that stops
garbage collection. In highly interactive environments, this may
result in your database file growing at a big rate and the operations
in the database being each time slower. As a corollary, having an
auto-commit transaction working for all the day or using only
CommitRetaining or simply opening a transaction that's not committed
for several hours without need is not a wise solution.
"
YES INDEED!
Regards,
Johan