Re: A thought on Index Organized Tables

From: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Karl Schnaitter <karlsch(at)gmail(dot)com>, pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A thought on Index Organized Tables
Date: 2010-02-26 04:33:35
Message-ID: 9362e74e1002252033t1fe97293y2a9a655233edb282@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 26, 2010 at 9:54 AM, Gokulakannan Somasundaram <
gokul007(at)gmail(dot)com> wrote:

>
> No, it's far from harmless. As soon as that heap TID gets filled with
>> an unrelated tuple, you run the risk of indexscans alighting on and
>> perhaps modifying the wrong tuple.
>>
>>
> Tom,
i think this will never happen. The only issue is when we need to go
back to the index from heap. This is to update the timestamps of
update/delete.

Gokul.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Hunsaker 2010-02-26 04:46:20 Re: Avoiding bad prepared-statement plans.
Previous Message Alex Hunsaker 2010-02-26 04:28:14 Re: Avoiding bad prepared-statement plans.