RPK wrote:
> How is PGSQL Locking compared with Oracle's MVCC? How PGSQL handles
> concurreny and how it differs with Oracle's Multi-Version Concurrency
> Control (MVCC)?
PostgreSQL uses MVCC.
http://www.postgresql.org/docs/8.2/static/mvcc.html
Joshua D. Drake
--
=== The PostgreSQL C
On 2/23/07, Tomas Vondra <[EMAIL PROTECTED]> wrote:
Sure, there are many differences when it comes to internals (Albe
Laurenz already pointed out the
most obvious one), as well as the Oracle is superior in many areas
(partitioning, some features in
PL/SQL, etc.).
This generally means that if you
How is PGSQL Locking compared with Oracle's MVCC? How PGSQL handles
concurreny and how it differs with Oracle's Multi-Version Concurrency
Control (MVCC)?
Well, I'm currently working on this comparison as we will need to port
and support some currently
Postgresql-only applications on several
> How is PGSQL Locking compared with Oracle's MVCC? How PGSQL handles
> concurreny and how it differs with Oracle's Multi-Version Concurrency
> Control (MVCC)?
In PostgreSQL, old rows remain in the table until the table is vacuumed.
In Oracle, old rows are kept in the 'undo table space' until - we
RPK wrote:
How is PGSQL Locking compared with Oracle's MVCC? How PGSQL handles
concurreny and how it differs with Oracle's Multi-Version Concurrency
Control (MVCC)?
The manuals are good for this type of thing:
http://www.postgresql.org/docs/8.2/static/mvcc.html
--
Richard Huxton
Archonet
