From: | "Chad Wagner" <chad(dot)wagner(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, RPK <rohitprakash123(at)indiatimes(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: New feature request: FlashBack Query |
Date: | 2007-02-18 00:43:23 |
Message-ID: | 81961ff50702171643u3042e8cfp8e17e7bd89507b51@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/17/07, elein <elein(at)varlena(dot)com> wrote:
>
> For other recent time travel ideas see:
> http://www.varlena.com/GeneralBits/122.php
> Time travel is not cheap, though.
>
I am sure this topic has probably been beaten to death in the past, but has
anyone talked about the advantages of Oracle's MVCC model versus
PostgreSQL's MVCC model? Oracle achieves multiversioning by using
rollback/undo segments, where PostgreSQL appears to place (essentially) the
undo in the same space as the table.
If I were to guess this is probably a major thing to change. Clearly there
are advantages to both, with Oracle essentially the space consumed by a
modified row is immediately available for reuse and generally there is
little row migration assuming there is enough space on the block so you
should be able to avoid updates to the index and the bloating that seems to
go along with vacuuming.
Is there any previous discussions that folks could point out here?
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-02-18 01:29:59 | Re: [HACKERS] pgsql: Add lock matrix to documentation. |
Previous Message | Jeremy Drake | 2007-02-18 00:10:20 | Re: patch adding new regexp functions |