> p> I was engaged in a debate about IB/FB's
> p> MVCC model and various other issues about
>
> Need some correction. InterBase's multiversion
> architecture is named as Multi-Generational Architecture
> (MGA). So, most of documents about Interbase refer to
> MGA, not MVCC.
>
> As to myself, I saw MVCC abbreviature at first in
> PostgreSQL. Seems that PGSQL copied MGA from InterBase
> (maybe not) and named it MVCC. It was done by some
> russion programmer, sorry don't remember his name (maybe
> it can be found at PGSQL sources).
>
> Right now
>
> - InterBase have MGA since 1985

v1, correct?

> - Oracle have versioning (named as semi-verisioning
> because it have some problems with very long snapshot
> transactions) since version 8.0 (am I right?).

No earlier. Reading in the newsgroup, they say since v3 or v4
or it got extended MVCC since v4.

Although I thought it was around v7 ...

> - PostgreSQL have MVCC since ... (don't know).
>
> - MS SQL 2005 will have versioning same as in InterBase/Firebird.

Not entirely sure -- it has _something_ like MGA.

> - MySQL will (? or already) have versioning ... don't know
> about it's implementation or limitations.

They have MVCC/MGA in its InnoDB storage system.

> These all show that commercial RDBMS' are moving to
> versioning systems. And this also shows that
> there is no new (extraordinal) thoughts in that area
> since 1983-1985.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com