Re: Optimizing Update with WHERE x IN (id1,id2,...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Optimizing Update with WHERE x IN (id1,id2,...)
Date: 2010-12-22 15:23:27
Message-ID: 5294.1293031407@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Michael Monnerie <michael(dot)monnerie(at)is(dot)it-management(dot)at> writes:
> I just saw this EXPLAIN in PostgreSQL 8.3.12:
> [ just like any other bitmap index scan ]
> And it seems to me that could be optimized to skip the "Recheck Cond" as
> that is already checked by the Index Scan? Should save some CPU cycles.

You evidently don't understand what that's for. In typical cases it's
not rechecked. The recheck condition is only applied if the index scan
becomes lossy.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Josh 2010-12-22 16:53:36 Securing a remotely accessible PostgreSQL server
Previous Message Viktor Bojović 2010-12-22 12:04:50 Re: how made procedure returned different types of value?