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

From Matthew Wakeling
Subject Re: Should the optimiser convert a CASE into a WHERE if it can?
Date
Msg-id alpine.DEB.2.00.1001271659000.6195@aragorn.flymine.org
Whole thread Raw
In response to Re: Should the optimiser convert a CASE into a WHERE if it can?  (Віталій Тимчишин <tivv00@gmail.com>)
Responses Re: Should the optimiser convert a CASE into a WHERE if it can?  (Віталій Тимчишин <tivv00@gmail.com>)
List pgsql-performance
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.

Matthew

--
 An optimist sees the glass as half full, a pessimist as half empty,
 and an engineer as having redundant storage capacity.

pgsql-performance by date:

Previous
From: Віталій Тимчишин
Date:
Subject: Re: Should the optimiser convert a CASE into a WHERE if it can?
Next
From: Віталій Тимчишин
Date:
Subject: Re: Should the optimiser convert a CASE into a WHERE if it can?