Re: Performance problems with postgres and null Values?
От | Sven Kerkling |
---|---|
Тема | Re: Performance problems with postgres and null Values? |
Дата | |
Msg-id | 002801d19fa4$3aa6adf0$aff409d0$@bds-online.com обсуждение исходный текст |
Ответ на | Re: Performance problems with postgres and null Values? (Albe Laurenz <laurenz.albe@wien.gv.at>) |
Список | pgsql-performance |
Thx. All queries are now running as usual. Thx for helping me. Best regards Sven -----Ursprüngliche Nachricht----- Von: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] Im Auftrag von Albe Laurenz Gesendet: Montag, 25. April 2016 10:08 An: 'Sven Kerkling *EXTERN*'; 'Merlin Moncure' Cc: 'postgres performance list' Betreff: Re: [PERFORM] Performance problems with postgres and null Values? 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
В списке pgsql-performance по дате отправления: