From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Josh Berkus" <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MVCC, undo log, and HOT |
Date: | 2007-10-23 13:13:22 |
Message-ID: | 36e682920710230613j5a4b6dbata786271a139666b0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/23/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > We never actually considred undo
>
> I did, but eventually ruled it out during the HOT design process. But
> then I considered a ton of other things and ruled them out also.
>
> Can't see a reason to bring it up again, so perhaps we should add it to
> the definitely don't want list. Don't *need* would be better.
Actually, my initial UNDO design and prototype had several other
advantages over HOT (better performance, inherent time-travel, smaller
on-disk footprint, and *no* vacuum). The major issue was due to the
amount of architecture changes Postgres would've required and Bruce's
advice regarding the community's inability to accept such a large and
complex change.
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2007-10-23 13:16:58 | Re: [PATCHES] Including Snapshot Info with Indexes |
Previous Message | Jonah H. Harris | 2007-10-23 13:07:52 | Re: MVCC, undo log, and HOT |