Re: [PERFORM] Optimization inner join

tests with Oracle and it uses a predicate in the query plan, removing the lines where b.b is null. In Oracle, it´s the same plan, with and without IS NOT NULL in the WHERE statement. -- Clailson Soares Dinízio de Almeida On 19/01/2017 09:34, Phillip Couto wrote: NULL is still a value that ma

[PERFORM] Optimization inner join

49 rows=600 loops=1)" "Total runtime: 1.248 ms" My question is: Why the planner isn't removing the null rows during the scan of table b? -- Clailson Soares Dinízio de Almeida