Re: Preventing index scans for non-recoverable index AMs

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Preventing index scans for non-recoverable index AMs
Date: 2008-12-18 09:40:27
Message-ID: 1229593227.4793.355.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Thu, 2008-12-18 at 08:29 +0200, Heikki Linnakangas 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.

Agreed.

> I think we should just leave it alone for 8.4, and fix it properly in a
> future relase by implementing WAL-logging for hash indexes.

You really think we should just leave it alone? That gives me less work,
so I will accept that if you think so. Gives me the shivers though.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2008-12-18 09:48:53 Re: Variadic parameters vs parameter defaults
Previous Message Simon Riggs 2008-12-18 09:35:09 Re: Sync Rep: First Thoughts on Code