Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 5FDD69FB479 for ; Mon, 26 Mar 2007 11:06:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 86344-09 for ; Mon, 26 Mar 2007 11:06:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by postgresql.org (Postfix) with ESMTP id C53BF9FB447 for ; Mon, 26 Mar 2007 11:06:00 -0300 (ADT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.8/8.13.8) with ESMTP id l2QE5o9L051400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 26 Mar 2007 07:05:52 -0700 (MST) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.8/8.13.8) with ESMTP id l2QE5nU5009382; Mon, 26 Mar 2007 08:05:49 -0600 (MDT) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.8/8.13.8/Submit) id l2QE5nb6009381; Mon, 26 Mar 2007 08:05:49 -0600 (MDT) (envelope-from mfuhr) Date: Mon, 26 Mar 2007 08:05:49 -0600 From: Michael Fuhr To: Gauri Kanekar Cc: pgsql-performance@postgresql.org Subject: Re: Nested Loop Message-ID: <20070326140549.GA9322@winnie.fuhr.org> References: <7e4ba9550703260504u6e9402ferd958620c79e9640a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7e4ba9550703260504u6e9402ferd958620c79e9640a@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/395 X-Sequence-Number: 23800 On Mon, Mar 26, 2007 at 05:34:39PM +0530, Gauri Kanekar wrote: > how to speedup nested loop queries and by which parameters. Please post a query you're trying to tune and the EXPLAIN ANALYZE output, as well as any changes you've already made in postgresql.conf or configuration variables you've set in a particular session. Without more information we can't give much advice other than to make sure you're vacuuming and analyzing the tables often enough to keep them from becoming bloated with dead rows and to keep the statistics current, and to review a configuration checklist such as this one: http://www.powerpostgresql.com/PerfList -- Michael Fuhr