Subject | Re: [firebird-support] garbage collect in backup |
---|---|
Author | Ann W. Harrison |
Post date | 2005-07-08T17:37:10Z |
c_pradelli wrote:
there's no benefit. If not, then removing unneeded back versions of
records will improve performance by limiting the growth of the database
and by avoiding the cost of garbage collection when the database is more
heavily used.
database - all transactions, including read-only transactions either
perform garbage collection or produce lists of work for a separate
garbage collection thread. It's just good housekeeping - life is more
pleasant if you clean up messes as you find them rather than waiting
until the mess is intolerable, then stopping everything and doing a
massive cleanup.
Regards,
Ann
>If you plan to replace the database with one restored from the backup,
> I have got some question about garbage collect and gbak:
>
> What is the benefit of do a garbage_collect on the database when I'm
> doing a backup with gbak?
there's no benefit. If not, then removing unneeded back versions of
records will improve performance by limiting the growth of the database
and by avoiding the cost of garbage collection when the database is more
heavily used.
> Are there any difference in the backup file that I obtain from gbakNone.
> if I use the -g[arbage_collect] switch or if I don't use it?
> Why garbage_collect is enabled by default in gbak if there are otherGarbage collection is enabled by default on all functions of the
> tools (gfix) for doing that explicitly?.
database - all transactions, including read-only transactions either
perform garbage collection or produce lists of work for a separate
garbage collection thread. It's just good housekeeping - life is more
pleasant if you clean up messes as you find them rather than waiting
until the mess is intolerable, then stopping everything and doing a
massive cleanup.
Regards,
Ann