On Thu, Dec 18, 2008 at 11:59 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote:
> > Right, this is certainly not a new problem. It's not even a new problem in > the context of replication or hot standby, because we already have the > problem with PITR and file-based log shipping. > > Also, it's not just a problem *during* the recovery. The index is just as > corrupt after the recovery has finished. > Just curious, how do we handle the case of corrupted hash index today ? 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) ? Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
