Re: Performance problems with postgres and null Values? - Mailing list pgsql-performance

From Albe Laurenz
Subject Re: Performance problems with postgres and null Values?
Date
Msg-id A737B7A37273E048B164557ADEF4A58B53843FFE@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Performance problems with postgres and null Values?  ("Sven Kerkling" <kerkling@bds-online.com>)
Responses Re: Performance problems with postgres and null Values?
List pgsql-performance
Sven Kerkling wrote:
> This one ist the burden, running at least 100 seconds:
> 
>     SELECT b.id, b.status
>     FROM export b, masterNew mb
>     WHERE mb.sperre IS NULL
>       AND mb.status IS NULL
>       AND b.id = mb.id
>     LIMIT 100;
> 
> http://explain.depesz.com/s/eAqG

I think the problem is here:

Bitmap Index Scan on masterNew_2016_pi_idx (cost=0.00..5.34 rows=181 width=0) (actual time=805.225..805.225
rows=4,764,537loops=1)
 

Perhaps you should ANALYZE "masterNew" to get better statistics.

Yours,
Laurenz Albe

pgsql-performance by date:

Previous
From: "Sven Kerkling"
Date:
Subject: Re: Performance problems with postgres and null Values?
Next
From: Merlin Moncure
Date:
Subject: Re: Performant queries on table with many boolean columns