| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MVCC, undo log, and HOT |
| Date: | 2007-10-22 02:14:41 |
| Message-ID: | 471C0791.40801@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
> Bruce Momjian wrote:
>> Those who have been with the community from long ago might remember
>> discussion about implementing a undo log. The big advantage of this is
>> that it allows UPDATE to _replace_ rows and limits the amount of cleanup
>> required for UPDATEs.
>>
>> I am hoping that with HOT we will no longer have any need to even
>> consider undo.
>>
>
> We were considering it?
I don't ever remember us considering it seriously.
>
> I certainly wasn't. I've enough experience with Oracle and InnoDB to
> see that an undo log is its own set of performane issues. No thanks.
>
It certainly does.
Joshua D. Drake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-22 02:21:36 | Rethinking ts_debug() output |
| Previous Message | Joshua D. Drake | 2007-10-22 02:12:58 | Re: Ready for beta2? |