Pardon my ignorance, but what exactly does "Firebird is eventually going to
stop
tracking it through its redo log" mean? Does it mean that when the log is
full, Firebird will not be able to rollback any more updates (it will behave
as if it was commiting them right away) or does it mean that it will
dropthose extra updates? Also, what is the critical factor for "filling up
the redo log"? Number of INSERTs? Number of queries? Number of changed
records? Total size of the changed records?

Thanks,

Pepak

----- Original Message -----
From: "Rick Debay" <rdebay@...>
To: <firebird-support@yahoogroups.com>
Sent: Thursday, August 24, 2006 5:04 PM
Subject: RE: [firebird-support] Batch insert performance


>I wouldn't bother committing at certain points, unless that makes sense
> from a data consistency point of view.
> For large amounts of data where Firebird is eventually going to stop
> tracking it through its redo log (I'm using the wrong term there) you
> can instruct Firebird to not maintain such a log.