Re: A thought on Index Organized Tables - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: A thought on Index Organized Tables
Date
Msg-id 9362e74e1002261126p10cb63c8j8795a561b94e7287@mail.gmail.com
Whole thread Raw
In response to Re: A thought on Index Organized Tables  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A thought on Index Organized Tables  (Gokulakannan Somasundaram <gokul007@gmail.com>)
Re: A thought on Index Organized Tables  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-hackers by date:

Previous
From: Mark Mielke
Date:
Subject: Re: Avoiding bad prepared-statement plans.
Next
From: Tom Lane
Date:
Subject: Re: Avoiding bad prepared-statement plans.