Thx.
All queries are now running as usual.
Thx for helping me.
Best regards
Sven
-Ursprüngliche Nachricht-
Von: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] Im Auftrag von Albe Laurenz
Gesendet: Montag, 25. April 2016 10:08
An: 'Sven Ker
-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] Im Auftrag von Merlin Moncure
Gesendet: Samstag, 23. April 2016 00:11
An: Sven Kerkling
Cc: postgres performance list
Betreff: Re: [PERFORM] Performance problems with postgres and null Values?
On Thu, Apr 21, 2016 at 4:49 AM
Total Cost: 716.61
Plan Rows: 181
Plan Width: 8
Recheck Cond: "((status IS NULL) AND (sperre IS NULL))"
Plans:
- Node Type: "Bitmap Index Scan"
Parent Relationship: "Outer"
Index Name: "masterNew_2016_pi_idx"
Startup Cost: 0.00
Total Cost: 5.34
Plan Rows: 181
Plan Width: 0
There we have our problem.
We have tried to fix it using a partial Index on _id_ with `status is null
and sperre is null` .
If we don't use `sperre is null` in this query it is quick. I think we have
these problems because _sperre_ and _status_ have much null values.
_status_: 67% null and _sperre_: 97% null .
On each table there are btree indexes on _id_, _sperre_ and _status_.
On _masterNew_ there is a partial Index on _id_ with `sperre is null and
status is null`.
Can somebody help me with these performance Problem.
What can I try to solve this?
Best regards,
Sven Kerkling
