Re: Slow execution time when querying view with WHERE clause - Mailing list pgsql-performance

From Jaime Casanova
Subject Re: Slow execution time when querying view with WHERE clause
Date
Msg-id 20041124054043.88464.qmail@web50002.mail.yahoo.com
Whole thread Raw
In response to Re: Slow execution time when querying view with WHERE clause  (Mike Mascari <mascarm@mascari.com>)
Responses Re: Slow execution time when querying view with WHERE clause
List 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

pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [pgsql-hackers-win32] scalability issues on win32
Next
From: Tom Lane
Date:
Subject: Re: Slow execution time when querying view with WHERE clause