| 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 21:01:58 |
| Message-ID: | 9362e74e1002261301y4be2c2avef253f88e384a695@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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.
>>
>>
> Tom,
if this is our goal - *"can return wrong query answers, but
should not corrupt the heap data.*" and if we make Thick indexes capable of
that, can i consider that as a thumbs up from your side? As you may already
know, this will only happen when there is a volatile function based index.
Heikki,
Please let me know, if you feel otherwise.
Thanks,
Gokul.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2010-02-26 21:06:10 | Re: Hot Standby query cancellation and Streaming Replication integration |
| Previous Message | Tom Lane | 2010-02-26 20:47:55 | Re: Avoiding bad prepared-statement plans. |