Skip site navigation (1) Skip section navigation (2)

Re: Faster with a sub-query then without

From: Martin Foster <martin(at)ethereal-realms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Faster with a sub-query then without
Date: 2004-08-15 16:01:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Tom Lane wrote:
> Martin Foster <martin(at)ethereal-realms(dot)org> writes:
>>The one not using sub-queries under EXPLAIN ANALYZE proves itself to be 
>>less efficient and have a far higher cost then those with the penalty of 
>>a sub-query.   Since this seems to be counter to what I have been told 
>>in the past, I thought I would bring this forward and get some 
> The ones with the subqueries are not having to form the full join of W
> and G; they just pick a few rows out of G and look up the matching W
> rows.
> The "subquery penalty" is nonexistent in this case because the
> subqueries are not dependent on any variables from the outer query, and
> so they need be evaluated only once, rather than once per outer-query
> row which is what I suppose you were expecting.  This is reflected in
> the EXPLAIN output: notice they are shown as InitPlans not SubPlans.
> The outputs of the InitPlans are essentially treated as constants (shown
> as $0 in the EXPLAIN output) and the outer plan is approximately what
> it would be if you'd written WHERE g.field = 'constant' instead of
> WHERE g.field = (select ...)
> 			regards, tom lane

That would explain it overall.  Still, it does seem unusual when one 
puts in additional code, which most literature warns you about and you 
actually gain a speed boost.


	Martin Foster
	Creator/Designer Ethereal Realms

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2004-08-15 17:21:30
Subject: Re: Slow joins against set-returning functions
Previous:From: Michael FuhrDate: 2004-08-15 16:00:14
Subject: Slow joins against set-returning functions

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group