in reply to Re^4: Perl/PostgreSQL niche
in thread Perl/PostgreSQL niche

This node falls below the community's threshold of quality. You may see it by logging in.

Replies are listed 'Best First'.
Re^6: Perl/PostgreSQL niche
by perrin (Chancellor) on Sep 06, 2005 at 16:16 UTC
    MySQL has had MVCC for several years. That's how the InnoDB engine works.
Re^6: Perl/PostgreSQL niche
by dbwiz (Curate) on Sep 06, 2005 at 16:16 UTC

    MVCC Multi-Version Concurrency Control is just a fancy name to signify transactions at "Repeatable Read" and "Serializable" isolation levels. I didn't care to mention all the manual to you. Just the basic facts.

    InnoDB has MVCC without that name. It provides full and reliable ACID compliant transactions. That's enough for me. If the fancy name is not in the manual, who cares?

      InnoDB is often referred to as having MVCC, so I don't think there's any reason to avoid the name. In addition to making those isolation levels possible, it allows readers to get a consistent state without waiting for writers, increasing the scalability of the system.