Re: Way to avoid expensive Recheck Cond in index lookup?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Matt Magoffin" <postgresql(dot)org(at)msqr(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Way to avoid expensive Recheck Cond in index lookup?
Date: 2007-12-18 22:24:06
Message-ID: 5795.1198016646@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Matt Magoffin" <postgresql(dot)org(at)msqr(dot)us> writes:
> The problem for me is, the Recheck Cond is then on the xpath() function
> used by the function-based index. My understanding is that then the
> database must actually call the xpath() function again on all matches from
> the index lookup.

This is mistaken. It only happens if there are so many hits that the
bitmap becomes lossy (which you can control to some extent anyway by
adjusting work_mem).

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Magoffin 2007-12-19 00:47:00 Re: Way to avoid expensive Recheck Cond in index lookup?
Previous Message Matt Magoffin 2007-12-18 21:35:46 Way to avoid expensive Recheck Cond in index lookup?