Received: from antares.mcs.anl.gov (mcs.anl.gov [140.221.9.6]) by hub.org (8.9.1/8.9.1) with SMTP id XAA29085 for ; Mon, 26 Oct 1998 23:17:15 -0500 (EST) (envelope-from selkovjr@mcs.anl.gov) Received: from mcs.anl.gov (selkovjr@slip55.slip.anl.gov [146.137.252.104]) by antares.mcs.anl.gov (8.6.10/8.6.10) with ESMTP id WAA27985; Mon, 26 Oct 1998 22:17:02 -0600 Message-Id: <199810270417.WAA27985@antares.mcs.anl.gov> To: pierre , pgsql-sql@postgreSQL.org Subject: Re: [SQL] Joining bug???? In-Reply-To: Your message of "Mon, 26 Oct 1998 21:39:44 CST." <199810270339.DAA95886@out5.ibm.net> Date: Mon, 26 Oct 1998 22:18:25 -0500 From: "Gene Selkov Jr." > I've been attempting to get my DB tuned to handle joins as best as > possible. However, no matter which way I try to perform the joins, if I > attempt to join more than two or three tables the joins becomes > unbearably long not matter how many indexes I create in however many ways. Ditto. Never saw a quadruple join succeed, even with relatively small tables. > My only solution was to create a hybrid table that contains the join of > all of the tables I'm searching on with multi-keyed indexes. This is a > VERY kludgy solution that makes changing the keys to my DB hard to change. The solution I use may be the worst imaginable kludge, but it works great: I do the joins (as well as other set operations) on the client side. Perl hashes are very good for that. --Gene