Re: Should the optimiser convert a CASE into a WHERE if it can? - Mailing list pgsql-performance

From Віталій Тимчишин
Subject Re: Should the optimiser convert a CASE into a WHERE if it can?
Date
Msg-id 331e40661001270909q3f6cdb5et17c9819b29d26b54@mail.gmail.com
Whole thread Raw
In response to Re: Should the optimiser convert a CASE into a WHERE if it can?  (Matthew Wakeling <matthew@flymine.org>)
List pgsql-performance


27 січня 2010 р. 19:01 Matthew Wakeling <matthew@flymine.org> написав:
On Wed, 27 Jan 2010, Віталій Тимчишин wrote:
How  about SELECT SUM (case when id > 1200000 and id < 1210000 then 1 end)
from tbl_tracker;

That is very interesting.


* All the functions should be noop for null input

Alas, not true for COUNT(*), AVG(), etc.

select avg(b), count(b), count(*) from (values (2),(null))a(b)
gives  (2.0, 1, 2) for me, so AVG is in game. Sure, it won't work for count(*), but optimizer already knows which aggregates are strict and which are not, so no new information is needed.

Best regards, Vitalii Tymchyshyn

pgsql-performance by date:

Previous
From: Matthew Wakeling
Date:
Subject: Re: Should the optimiser convert a CASE into a WHERE if it can?
Next
From: James Mansion
Date:
Subject: Re: Benchmark shows very slow bulk delete