Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 2FC46476673 for ; Wed, 15 Jan 2003 23:41:53 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id 550284766CB for ; Wed, 15 Jan 2003 23:41:04 -0500 (EST) Received: from [63.195.55.98] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 4.0.2) with HTTP id 2315724; Wed, 15 Jan 2003 20:41:11 -0800 From: "Josh Berkus" Subject: Re: 7.3.1 New install, large queries are slow To: Tom Lane , "Roman Fail" Cc: josh@agliodbs.com, pgsql-performance@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.4.0.2 Date: Wed, 15 Jan 2003 20:41:11 -0800 Message-ID: In-Reply-To: <11547.1042691700@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/131 X-Sequence-Number: 778 Tom, Roman, > I think more likely the issue is that your use of JOIN syntax is > forcing > Postgres into a bad plan. MSSQL probably doesn't assign any semantic > significance to the use of "a JOIN b" syntax as opposed to "FROM a, > b" > syntax. That's correct. MSSQL will reorder equijoins, even when explicitly declared. Hey, Roman, how many records in BatchDetail, anyway? Josh Berkus