From: Tom Lane <tgl@sss.pgh.pa.us>
To: Remigiusz Sokolowski <rems@gdansk.sprint.pl>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] indexes
Date: Tue, 01 Jun 1999 10:04:59 -0400
Message-ID: <21255.928245899@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GS4.4.02A.9906010826460.18822-100000@netra.gdansk.sprint.pl>
Remigiusz Sokolowski <rems@gdansk.sprint.pl> writes:
> But without Vadim's suggestion I've got still similar results - sometimes
> optimizer has used index on e1 and on b1, sometimes on e1 and e2, but
> never on e1,b1 and e2 at once (note: this was join on ent e1, binds b1 and
> ent e2)
You won't ever see a three-way join in EXPLAIN's output, if that was
what you were looking for. Postgres always handles joins by combining
two tables, then combining the result with another table, etc.
regards, tom lane
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rems@gdansk.sprint.pl
Subject: Re: [SQL] indexes
In-Reply-To: <21255.928245899@sss.pgh.pa.us>
* 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