Hello Jim,

Saturday, October 19, 2002, 6:40:21 PM, you wrote:

>>2) It's unreliable. Just kill the server while a database is being GC'ed and
>>most likely you'll have your database corrupted. Just a real-world example.
>>Someone does a mass update/delete, then start a complex report, then wait
>>10, 20, 30 minutes - the server is 100% busy. One kills the connection - the
>>server is still 100% busy. One kills the server - and get the database
>>corrupted.
>>

> That's gibberish. The backout code is careful write like everything
> else, so the database wouldn't work at all. And it's the same code
> whether kicked off by the GC thread or a worker thread.

>>Comments anyone? Are these unavoidable effects of the current design?
>>

> The effects are not only avoidable, but avoided.

There is a memory corruption problem in IB6/FB1 that possibly lead to
crashes or random database corruption during all kinds of garbage collection.
It is fixed in FB1.5. Maybe somebody wants to backport that fixes to
FB1 ?

> Jim Starkey

--
Best regards,
Nickolay Samofatov mailto:skidder@...