--- In firebird-support@yahoogroups.com, "DataCom - Diego Moreira da
Rosa" <diego@d...> wrote:

> Hi all,
>
> has any of you ever had problems with extreme growing of the data

base using

> IB/Firebird?

Those who design their applications to hold opened transactions for
a long time, what prevent collection of garbage within database and
repeated usage of freed pages. Read_commited read only transactions
are excluded from this rule.

> We are thinking it has something to do with multiple

threads

> accessing the data base (our application has various threads reading

and

> writing the DB).

Multithreaded access usually entirely works or entirely not. If you
have separated connection for each thread or properly serialized
inside application usage of one connection from different thread - it
works. For server there are not differences who control connection and
transactions within it - process or thread. Check your transactions
management to don't hold opened writeable transactions when it is not
required by nature of model served by your application. Pay attention
to subject discussed nearby here - Oldest Active Transaction and Next
Transaction.

Best regards, Alexander.