At 11:57 AM 2/7/2002 -0500, nprasad3@... wrote:

>Each trunk on the system has a record in the database. The trunk stores
>valuable statistics in this row (frequent updates). PostgreSQL creates
>a new record on a UPDATE (something some database guru called MVCC).
>Problem is self evident, a busy trunking system would probably do over
>100 updates a second. Performance degradation leads to gradual collapse
>and vacuuming the database is worse as it locks the tables and freezes
>the system.

Yes, InterBase uses MVCC - multi-version concurrency control - and
has for 15 years. Unlike postgreSQL, we "vacuum" or as we say
"garbage collect" automatically and continuously. Providing that
you commit each update transaction and don't leave other transactions
open for long periods of time, InterBase/Firebird should work well.

Regards,

Ann