X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 73A3DD1B530 for ; Mon, 29 Sep 2003 14:02:57 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 89536-02 for ; Mon, 29 Sep 2003 11:02:33 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id A6DB3D1B51D for ; Mon, 29 Sep 2003 11:02:29 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h8TE2ThK049515 for ; Mon, 29 Sep 2003 14:02:29 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h8TDWaRB044386 for pgsql-performance@postgresql.org; Mon, 29 Sep 2003 13:32:36 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: avoiding seqscan? Date: Mon, 29 Sep 2003 15:32:31 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 18 Message-ID: <3F78346F.5060809@bigfoot.com> References: <95900000.1064782481@palle.girgensohn.se> <3F7766B3.4030705@bigfoot.com> <180710000.1064841936@durian.pingpong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Palle Girgensohn User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en In-Reply-To: <180710000.1064841936@durian.pingpong.net> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/354 X-Sequence-Number: 3720 Palle Girgensohn wrote: > Will that make a difference? From what I've seen, it does not make much > difference, but I have seen queries speed up when rewritten explicit > joins. I guess it depends on other things, but is it really so that the > explicit joins are bad somehow? Do you have any pointers to > documentation about it, if so? > > Thanks, > Palle Are not absolutelly bad but sometimes that path that you choose is not the optimal, in postgres 7.4 use the explicit join will be less limitative for the planner. Regards Gaetano Mendola