Message-ID: <4580025D.2040903@freesurf.fr>
Date: Wed, 13 Dec 2006 14:38:37 +0100
From: Arnaud Lesauvage <thewild@freesurf.fr>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jens Schipkowski <jens.schipkowski@apus.co.at>
CC: pgsql-performance@postgresql.org
Subject: Re: Slow update with simple query
References: <457FDB1E.6040801@freesurf.fr>
 <op.tkhy4jpg81rjf6@xjens.apus.local>
	<457FF0CD.4050606@freesurf.fr> <op.tkh10qgw81rjf6@xjens.apus.local>
In-Reply-To: <op.tkh10qgw81rjf6@xjens.apus.local>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Jens Schipkowski a écrit :
> On Wed, 13 Dec 2006 13:23:41 +0100, Arnaud Lesauvage <thewild@freesurf.fr>  
>> Why is this query better than the other one ? Because it runs the  
>> "(field IN ('some','other') AND field2 = 'Y')" once and then executes  
>> the join with the resulting set ?
> True. The Subselect in FROM clause will be executed once and will be  
> joined using the condition at where clause. So your condition at t2 is not  
> executed for each row in t1(2mio records) but for each row in t2(1k  
> records). And the boolean value is already set during update.

OK Jens, thanks for clarifying this.
I thought the planner could guess what to do in such cases.

Regards
--
Arnaud