From: Tomasz Myrta <jasiek@klaster.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Lista dyskusyjna pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: explicit joins wrong planning
Date: Sat, 29 Nov 2003 00:05:14 +0100
Message-ID: <3FC7D4AA.80900@klaster.net> (raw)
In-Reply-To: <1517.1070056638@sss.pgh.pa.us>
References: <3FC63057.3080009@klaster.net>
<29784.1070047126@sss.pgh.pa.us>
<3FC7A565.4000104@klaster.net>
<296.1070049123@sss.pgh.pa.us>
<3FC7AC6F.7080603@klaster.net>
<1517.1070056638@sss.pgh.pa.us>
Dnia 2003-11-28 22:57, Użytkownik Tom Lane napisał:
> Restructure planning of nestloop inner indexscans so that the set
> of usable joinclauses is determined accurately for each join.
> Formerly, the code only considered joinclauses that used all of the
> rels from the outer side of the join; thus for example FROM (a
> CROSS JOIN b) JOIN c ON (c.f1 = a.x AND c.f2 = b.y) could not
> exploit a two-column index on c(f1,f2), since neither of the qual
> clauses would be in the joininfo list it looked in. The new code
> does this correctly, and also is able to eliminate redundant
> clauses, thus fixing the problem noted 24-Oct-02 by Hans-Jürgen
> Schönig.
Yes, this is a description of my problem. Thanks a lot.
Regards,
Tomasz Myrta
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: jasiek@klaster.net, tgl@sss.pgh.pa.us
Subject: Re: explicit joins wrong planning
In-Reply-To: <3FC7D4AA.80900@klaster.net>
* 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