From: | "Alexander Staubo" <alex(at)purefiction(dot)net> |
---|---|
To: | "Harpreet Dhaliwal" <harpreet(dot)dhaliwal01(at)gmail(dot)com> |
Cc: | "Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Vacuum DB in Postgres Vs similar concept in other RDBMS |
Date: | 2007-05-23 17:59:08 |
Message-ID: | 88daf38c0705231059t6d6cddbcnbc563ceb294fd722@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/23/07, Harpreet Dhaliwal <harpreet(dot)dhaliwal01(at)gmail(dot)com> wrote:
> I was wondering if Vacuum DB concept in Postgres is really novel and there's
> no concept like this in other RDBMS like oracle or sql server.
> If at all other RDBMS have such a concept implemented, how good or bad it is
> as compared to postgres's vacuum db concept.
As we told you the last time you asked
(http://archives.postgresql.org/pgsql-general/2007-05/msg00074.php)
the concept of vacuuming is not unique to PostgreSQL by far. It is an
inherent facet of MVCC.
Other databases that implement MVCC, or implement an MVCC-like system
that requires garbage collection, include Oracle, SQLite, Firebird and
its parent project InterBase. Wikipedia has a decent article on MVCC:
http://en.wikipedia.org/wiki/Multiversion_concurrency_control
Alexander.
From | Date | Subject | |
---|---|---|---|
Next Message | André Volpato | 2007-05-23 18:28:28 | Remove query results from cache |
Previous Message | Magnus Hagander | 2007-05-23 17:52:10 | Re: [Re] Re: [Re] Re: Winsock error 10035 while trying to upgrade from 8.0 to 8.2 |