Re: Slow execution time when querying view with WHERE clause

Jaime Casanova <systemguards@yahoo.com>

From: Jaime Casanova <systemguards@yahoo.com>
To: pgsql-performance@postgresql.org
Date: 2004-11-24T05:40:43Z
Lists: pgsql-performance
 --- Mike Mascari <mascarm@mascari.com> escribió: 
> Tom Lane wrote:
> > Mike Mascari <mascarm@mascari.com> writes:
> > 
> >>When I query the view with a simple filter, I get:
> > 
> > 
> >>explain analyze select * from p_areas where
> deactive is null;
> > 
> > 
> > The problem seems to be here:
> > 
> > 
> >>    ->  Seq Scan on _areas a  (cost=0.00..2.48
> rows=1 width=163) (actual time=0.037..0.804 rows=48
> loops=1)
> >>          Filter: (deactive IS NULL)
> > 
> > 
> > Why is it so completely off about the selectivity
> of the IS NULL clause?

null values are not indexable, is that your question?
If it is your question then create a partial index
with where deactive is null.

regards,
Jaime Casanova

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com