Re: Any way to favor index scans, but not bitmap index scans? - Mailing list pgsql-general

From Tom Lane
Subject Re: Any way to favor index scans, but not bitmap index scans?
Date
Msg-id 10265.1216844863@sss.pgh.pa.us
Whole thread Raw
In response to Re: Any way to favor index scans, but not bitmap index scans?  ("Francisco Reyes" <lists@stringsutils.com>)
List pgsql-general
"Francisco Reyes" <lists@stringsutils.com> writes:
> On 3:37 pm 07/23/08 Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> You might be more likely to get a sane plan if you had an index on
>> join_ids.customer_id.

> There is an index in join_ids:
> joinids_customerids_joinid" btree (customer_id, joinid) WITH (fillfactor=98)

[ squint... ]  That makes no sense at all; it should certainly have
picked that index and not join_ids_join_id for a scan with a condition
on customer_id.  What is the datatype of the customer_id column exactly?
(Actually, if you could show us the whole schema of both these tables,
such as their psql \d descriptions, that would be helpful.)

            regards, tom lane

pgsql-general by date:

Previous
From: "Francisco Reyes"
Date:
Subject: Re: Any way to favor index scans, but not bitmap index scans?
Next
From: "Francisco Reyes"
Date:
Subject: Re: Any way to favor index scans, but not bitmap index scans?