From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | "Thomas Kellerer" <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: MVCC and index-only read |
Date: | 2008-11-18 20:09:57 |
Message-ID: | dcc563d10811181209q12f10a18kaaf280e78649ace0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Nov 18, 2008 at 1:07 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Tue, Nov 18, 2008 at 1:03 PM, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com> wrote:
>> On Tue, Nov 18, 2008 at 2:57 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>>> Sounds like they're borrowing the code from innodb that does much the
>>> same thing. In Innodb, if a field is indexed, it lives only as an
>>> index, not in the table and an index at the same time.
>>
>> They aren't borrowing anything, Oracle has had this functionality
>> since at least Oracle 8i (1999).
>
> Whoa, calm down Francis. I'm not suggesting they stole it or
> something. Just that they're using the same basic concepts.
Oh, and citation needed. I don't remember seeing anything about
oracle using indexes as sole storage units back in 8i
--
When fascism comes to America, it will be draped in a flag and
carrying a cross - Sinclair Lewis
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2008-11-18 20:27:33 | Re: MVCC and index-only read |
Previous Message | Scott Marlowe | 2008-11-18 20:07:44 | Re: MVCC and index-only read |