From: Richard Huxton <dev@archonet.com>
To: Edison Azzi <edisonazzi@terra.com.br>
Cc: pgsql-performance@postgresql.org
Subject: Re: Join the same row
Date: Wed, 07 Dec 2005 18:55:04 +0000
Message-ID: <43973008.2000708@archonet.com> (raw)
In-Reply-To: <43972DB8.90400@terra.com.br>
References: <4395F317.4040806@terra.com.br>
<4396AB05.2010806@archonet.com>
<43972DB8.90400@terra.com.br>
Edison Azzi wrote:
> Richard Huxton escreveu:
>> However, even if you removed the condition on origem, I don't think
>> the planner will notice that it can eliminate the join. It's just too
>> unusual a case for the planner to have a rule for it.
>>
>> I might be wrong about the planner - I'm just another user. One of the
>> developers may correct me.
>
>
> You are rigth, the planner will not eliminate the join, see:
>
> select * from cta_pag a, cta_pag p where a.nrlancto=p.nrlancto and
> p.nrlancto = 21861;
>
> EXPLAIN:
> Nested Loop (cost=0.00..11.48 rows=1 width=816)
> -> Index Scan using cta_pag_pk on cta_pag a (cost=0.00..5.74 rows=1
> width=408)
> Index Cond: (21861::numeric = nrlancto)
> -> Index Scan using cta_pag_pk on cta_pag p (cost=0.00..5.74 rows=1
> width=408)
> Index Cond: (nrlancto = 21861::numeric)
>
>
> I know that this is too unusual case, but I hoped that the planner could
> deal
> with this condition. I´m trying to speed up without have to rewrite a
> bunch of
> queries. Now I'll have to think another way to work around this issue.
Is the performance really so bad? All the data is guaranteed to be
cached for the second index-scan.
--
Richard Huxton
Archonet Ltd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dev@archonet.com, edisonazzi@terra.com.br
Subject: Re: Join the same row
In-Reply-To: <43973008.2000708@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox