Reg Me Please wrote:
Here it comes:
Aggregate (cost=227.59..227.61 rows=1 width=8)
-> Nested Loop (cost=0.00..227.34 rows=49 width=8)
-> Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
Filter: (fld1 = 'VEND'::text)
-> Index Scan using i_T1_partial on T1
On Friday 09 January 2009 20:00:57 Tom Lane wrote:
> Reg Me Please writes:
> > Aggregate (cost=227.59..227.61 rows=1 width=8)
> >-> Nested Loop (cost=0.00..227.34 rows=49 width=8)
> > -> Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
> >Filter: (fld1 = 'VEND'::t
On Friday 09 January 2009 20:00:36 Thomas Pundt wrote:
> Reg Me Please wrote:
> > Here it comes:
> >
> > Aggregate (cost=227.59..227.61 rows=1 width=8)
> >-> Nested Loop (cost=0.00..227.34 rows=49 width=8)
> > -> Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
> >
Reg Me Please writes:
> Aggregate (cost=227.59..227.61 rows=1 width=8)
>-> Nested Loop (cost=0.00..227.34 rows=49 width=8)
> -> Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
>Filter: (fld1 = 'VEND'::text)
> -> Index Scan using i_T1_partial on T1 (cos
Here it comes:
Aggregate (cost=227.59..227.61 rows=1 width=8)
-> Nested Loop (cost=0.00..227.34 rows=49 width=8)
-> Seq Scan on T2 (cost=0.00..1.07 rows=6 width=4)
Filter: (fld1 = 'VEND'::text)
-> Index Scan using i_T1_partial on T1 (cost=0.00..37.61 row
Could you provide the output of EXPLAIN ANALYZE with your query?
On Fri, Jan 9, 2009 at 7:06 PM, Reg Me Please wrote:
> Hi.
>
> For an INNER JOINed query, EXPLAIN says that a "nested loop" is responsible
> for the big part of the time needed to run.
>
> The 2 tables JOINed are:
>
> T1: multi-mill
Hi.
For an INNER JOINed query, EXPLAIN says that a "nested loop" is responsible
for the big part of the time needed to run.
The 2 tables JOINed are:
T1: multi-million rows
T2: few dozens rows
The join is though a single column in both sides and it's NOT a PK in either
table. But I have indexes
