From: | Ragnar <gnari(at)hive(dot)is> |
---|---|
To: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr> |
Cc: | Jens Schipkowski <jens(dot)schipkowski(at)apus(dot)co(dot)at>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Slow update with simple query |
Date: | 2006-12-13 14:49:00 |
Message-ID: | 1166021340.6369.103.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On mið, 2006-12-13 at 14:38 +0100, Arnaud Lesauvage wrote:
> Jens Schipkowski a écrit :
> > On Wed, 13 Dec 2006 13:23:41 +0100, Arnaud Lesauvage <thewild(at)freesurf(dot)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.
don't worry, it will.
this is not your problem
gnari
From | Date | Subject | |
---|---|---|---|
Next Message | Arnaud Lesauvage | 2006-12-13 15:19:55 | Re: Slow update with simple query |
Previous Message | Arnaud Lesauvage | 2006-12-13 13:38:37 | Re: Slow update with simple query |