Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA33752 for ; Wed, 7 Jul 1999 14:02:05 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id OAA05018; Wed, 7 Jul 1999 14:01:10 -0400 (EDT) From: Bruce Momjian Message-Id: <199907071801.OAA05018@candle.pha.pa.us> Subject: Re: [SQL] Good Optimization In-Reply-To: from Jan Wieck at "Jul 7, 1999 07:22:57 pm" To: Jan Wieck Date: Wed, 7 Jul 1999 14:00:57 -0400 (EDT) CC: secret , pgsql-sql@postgreSQL.org, johnridout@ctasystems.co.uk X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > There is a simple way to optimize SQL queries involving joins to > > PostgreSQL that I think should be handled by Postgre? If one is joining > > a tables a,b on attribute "x" and if one has something like x=3 then it > > helps A LOT to say: a.x=3 and b.x=3 in addition to saying a.x=b.x ... > > The example below shoulds the radical speed gain of doing this, and I > > think it isn't something real obvious to most people... > > > > Of course it could just be a common thing to do in SQL, anyway, just > > thought I'd let you all know what I discovered. > > > > > > > > Here is an example: > > [...] > > Hmmmmm, > > wouldn't it be nice to do such things automagically > (rewriter? planner?). Added to TODO: * In WHERE x=3 AND x=y, add y=3 -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026