Re: Preventing index scans for non-recoverable index AMs - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Preventing index scans for non-recoverable index AMs
Date
Msg-id 1229569017.4793.302.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Preventing index scans for non-recoverable index AMs  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Wed, 2008-12-17 at 23:28 -0300, Alvaro Herrera wrote:

> Hmm, it doesn't seem like you understood my suggestion ... basically I'm
> saying that a hash index insert/delete should put out this WAL record:
> 
> HEAP update address-of-pg_index-tuple set indisvalid=false
> 
> (I'm just guessing at indisvalid but you get my point)

That would be simple and I'm very sorry to say I still don't think it
would work. But yes, I did misunderstand you.

In-progress hash index scans would not be prevented from executing by
the WAL record, so you might end up following a bad pointer. We probably
wouldn't want to try killing anybody using index either, since that
would end up as a complete bloodbath.

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



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Infrastructure changes for recovery (v8)
Next
From: ITAGAKI Takahiro
Date:
Subject: Re: Looking for someone with MinGW