-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jonah H. Harris wrote:
> On 8/10/07, Jeff Davis <pgsql@j-davis.com> wrote:
>> Is there a document explaining more of the differences between the
>> postgresql MVCC model and something closer to InnoDB or Oracle, where it
>> has rollback segments? I'm interested in the design tradeoffs between
>> the two ideas.
>
> Not really, but the best reference is Transactional Information
> Systems: Theory, Algorithms, and the Practice of Concurrency Control
> by Weikum & Vossen.
I have this book. It is a very good book. It can also make your brain hurt.
Joshua D. Drake
> PostgreSQL uses multi-version timestamp ordering
> (MVTO) and Oracle/InnoDB use multi-version read consistency (MVRC).
> The main difference is that PostgreSQL is with-REDO/no-UNDO because it
> stores every row version in the main table, and Oracle/InnoDB are
> with-REDO/with-UNDO and they reconstruct a block and/or row image from
> the log to provide read consistency.
>
- --
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGvS5gATb/zqfZUUQRAnuzAKClGrTcks1twLjFiwvyQ9vXFKZw0ACgkbWy
YXbtLNMkQPM2ZtVxj7MmnKc=
=53cN
-----END PGP SIGNATURE-----
