Re: Using index for IS NULL query

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: Andrus <kobruleht2(at)hot(dot)ee>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Using index for IS NULL query
Date: 2008-11-11 21:01:58
Message-ID: 4919F2C6.4000303@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Index is not used for
>
> is null
>
> condition:
>
> create index makse_dokumnr_idx on makse(dokumnr);
> explain select
> sum( summa)
> from MAKSE
> where dokumnr is null
>
> "Aggregate (cost=131927.95..131927.96 rows=1 width=10)"
> " -> Seq Scan on makse (cost=0.00..131927.94 rows=1 width=10)"
> " Filter: (dokumnr IS NULL)"
>
>
> Table makse contains 1200000 rows and about 800 rows with dokumnr is
> null so using index is much faster that seq scan.
> How to fix ?

Yes, NULL values are not stored in the index, but you may create
functional index on

(CASE WHEN dokumnr IS NULL THEN -1 ELSE dokumnr END)

and then use the same expression in the WHERE clause. You may replace
the '-1' value by something that's not used in the dokumnr column.

regards
Tomas

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim 'Decibel!' Nasby 2008-11-11 22:42:57 Re: Oddity with view (now with test case)
Previous Message Andreas Kretschmer 2008-11-11 20:50:49 Re: Using index for IS NULL query