Message-Id: <4BFE8F4F0200002500031BA2@gw.wicourts.gov>
Date: Thu, 27 May 2010 15:27:11 -0500
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: <pgsql-performance@postgresql.org>,
	"Carlo Stonebanks" <stonec.register@sympatico.ca>
Subject: Re: Does FILTER in SEQSCAN short-circuit AND?
References: <hsv49v$312j$1@news.hub.org>
In-Reply-To: <hsv49v$312j$1@news.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

"Carlo Stonebanks" <stonec.register@sympatico.ca> wrote:
 
> SELECT *
> FROM MyTable
> WHERE foo = 'bar' AND MySlowFunc('foo') = 'bar'
> 
> Let's say this required a SEQSCAN because there were no indexes to
> support column foo. For every row where foo <> 'bar' would the
> filter on the SEQSCAN short-circuit the AND return false right
> away, or would it still execute MySlowFunc('foo') ?
 
For that example, I'm pretty sure it will skip the slow function for
rows which fail the first test.  A quick test confirmed that for me.
If you create a sufficiently slow function, you shouldn't have much
trouble testing that yourself.  :-)
 
-Kevin