Re: Partial index causing wrong results to be returned on 8.1.3 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Partial index causing wrong results to be returned on 8.1.3
Date
Msg-id 24003.1156825214@sss.pgh.pa.us
Whole thread Raw
In response to Partial index causing wrong results to be returned on 8.1.3  (Greg Sabino Mullane <greg@turnstep.com>)
Responses Re: Partial index causing wrong results to be returned on 8.1.3  ("Greg Sabino Mullane" <greg@turnstep.com>)
List pgsql-bugs
Greg Sabino Mullane <greg@turnstep.com> writes:
> I could not duplicate this on any identical database, but thought I
> would report it here, just for completeness. I've tried reindexing,
> vacuuming, etc. Explain plans all look normal.

Possibly explained by this 8.1.4 fix?

2006-05-18 14:57  tgl

    * src/backend/optimizer/plan/: createplan.c (REL8_1_STABLE),
    createplan.c: When a bitmap indexscan is using a partial index, it
    is necessary to include the partial index predicate in the scan's
    "recheck condition".  Otherwise, if the scan becomes lossy for lack
    of bitmap memory, we would fail to enforce that returned rows
    satisfy the predicate.    Noted while studying bug #2441 from Arjen
    van der Meijden.

If it gives right answers after you increase work_mem sufficiently,
I'd bet on this one ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Partial index causing wrong results to be returned on 8.1.3
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Partial index causing wrong results to be returned on 8.1.3