Subject | Re: Controlling expansion of database file / grow-by option? |
---|---|
Author | nocsav |
Post date | 2005-06-01T15:20:13Z |
We don't have many long running operations... but our application
autocommits almost everything. We have a lot of situations where the
database file is huge compared to the backup file.
Sounds like we should change our app to make longer transactions.
In the meantime, should we consider more frequent sweeping?
Thanks!
David
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
[...]
autocommits almost everything. We have a lot of situations where the
database file is huge compared to the backup file.
Sounds like we should change our app to make longer transactions.
In the meantime, should we consider more frequent sweeping?
Thanks!
David
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
[...]
> Add to that the common problem of long-running transactions. If theautocommit,
> client starts a transaction that never commits or only use
> then lots of old versions of records will never be removed. Checkthe
> gap between oldest active transaction and next transaction to findthe
> whether this is an additional problem (it would also be visible by
> file size being considerably reduced through backup/restore).