Re: [EXPLAIN] Nested loops

From: "Victor Nawothnig" <victor(dot)nawothnig(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: [EXPLAIN] Nested loops
Date: 2009-01-09 18:22:28
Message-ID: 9ad9b6b70901091022w6c33d3d4o22850079eb0cf273@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Could you provide the output of EXPLAIN ANALYZE with your query?

On Fri, Jan 9, 2009 at 7:06 PM, Reg Me Please <regmeplease(at)gmail(dot)com> 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-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 in both T1 and T2 for that column.
>
> I've read in the "Explaining EXPLAIN" by Rober Treat
> (at http://wiki.postgresql.org/wiki/Image:OSCON2005-ExplainingExplain.sxi)
> that this nested loop can be slow because of lacking of indexes.
>
> Is there any hint to try to speed that query up?
>
> As of now, only a REINDEX can help thanks to caching, I presume.
> But the EXPLAIN still says there's a slow nested loop.
>
> --
> Fahrbahn ist ein graues Band
> weisse Streifen, grüner Rand
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-01-09 18:22:43 Re: Improving compressibility of WAL files
Previous Message Reg Me Please 2009-01-09 18:06:27 [EXPLAIN] Nested loops