🚀 go-pugleaf

Magnus Flysjv wrote:

> I have the same problem.
> But this is on a 6.0.2.0 version.
> 
> We have an application that never commited as often as it should.
> When the application is close and commit was called, we lost all data
> and I have no idea why.

Did you run gfix on the database to see if it has become corrupt?

Are you sure you committed all active transactions before the
application was closed? If you close the program with a transaction
active it will be rolled back, not committed.

> 
> Also, the GDB file grown very fast.. but if I use gbak and gfix, the
> file is shrinken from 32MB to only 2MB.

Long running transactions disable garbage collection. This allows
garbage record versions to accumulate in the database if you hare doing
a lot of updates or deletes which, in turn, will cause the database
file to grow.

> 
> Can anyone smart confirm if there will be a problem if data isn't
> commited often?

There can be problems, depending on your transaction volume and whether
you are performing a a lot of updates and deletes or not but this will
not cause data to disappear.

-- 
Bill Todd (TeamB)