Re: Index not used, performance problem - Mailing list pgsql-performance

From Andreas Kostyrka
Subject Re: Index not used, performance problem
Date
Msg-id 1048957151.7543.19.camel@andi-lap
Whole thread Raw
In response to Re: Index not used, performance problem  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: Index not used, performance problem  (Matt Mello <alien@spaceship.com>)
Re: Index not used, performance problem  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-performance
On Sat, 2003-03-29 at 14:47, Christopher Kings-Lynne wrote:
> Hi Andreas,
>
> A few points:
>
> PostgreSQL is rarely going to use an index for a boolean column.  The
> reason is that since almost by definition true will occupy 50% of the rows
> and false will occupy 50% (say).  In this case, a sequential scan is
> always faster.  You would say that the 'selectivity' isn't good enough.
Well, perhaps it should collect statistics, because a "deleted" column
is a prime candidate for a strongly skewed population.

Andreas

Attachment

pgsql-performance by date:

Previous
From: Jord Tanner
Date:
Subject: Re: Index not used, performance problem
Next
From: Matt Mello
Date:
Subject: Re: Index not used, performance problem