| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Kenneth Marshall <ktm(at)rice(dot)edu>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Preventing index scans for non-recoverable index AMs |
| Date: | 2008-12-18 12:32:03 |
| Message-ID: | 494A42C3.3020408@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavan Deolasee wrote:
> Just curious, how do we handle the case of corrupted hash index today?
We don't.
> If we can detect that the index is corrupt because of bad page
> headers etc, then its still OK; we can throw an error. But what if the
> hash index is used after recovery and it returns wrong tuple(s) ?
You get to keep both pieces..
In short, don't use hash index, unless you're prepared to run REINDEX
manually after every crash.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2008-12-18 12:45:20 | Re: Preventing index scans for non-recoverable index AMs |
| Previous Message | Pavan Deolasee | 2008-12-18 12:18:34 | Re: Preventing index scans for non-recoverable index AMs |