Skip site navigation (1) Skip section navigation (2)

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: Greg Stark <gsstark(at)mit(dot)edu>, 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 19:26:11
Message-ID: 9362e74e1002261126p10cb63c8j8795a561b94e7287@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> It does.  The point is that the system is set up to limit the bad
> consequences.  You might (will) get wrong query answers, but the
> heap data won't get corrupted.
>
>
Again Tom, if there is an update based on index scan, then it takes the
tupleid and updates the wrong heap data right?
The only difference between normal index and thick index is to reach back to
the same index tuple to update the snapshot. How will that corrupt the heap
data? Did you intend to say that it corrupts the index data?

Thanks,
Gokul.

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-26 19:57:56
Subject: Re: Avoiding bad prepared-statement plans.
Previous:From: Mark MielkeDate: 2010-02-26 19:23:22
Subject: Re: Avoiding bad prepared-statement plans.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group