Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 0A1129F9DCA for ; Mon, 29 Oct 2007 12:22:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 29713-02 for ; Mon, 29 Oct 2007 12:22:15 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by postgresql.org (Postfix) with ESMTP id 6EF3C9F9B9B for ; Mon, 29 Oct 2007 12:22:13 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so1001877ugf for ; Mon, 29 Oct 2007 08:22:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=Ai4WV9KjGQ4U7y+0F/xfe5Zxy/1ZvsgNmtApB+5ByYs=; b=JPPiBCnj21JhtMPA2QZj1p7hCzhaU5WHJyZ7Q+aMCZHpFi55IWtrxC75zqH97SFb1QQeZaRHTcHjLc+bOK1O98r/8ZG21w3fg12GesLw+ig//nlpt52Uf9F03K9NNzV6oc9ZEZRHOYZDBYp5VDQuQNqZc+9e+vZ9TQJgEK9q3SY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=Rk9/UeHoX8BBKB9VTeeAhn9fVOxXSHUFQbtzqaNg7EtknBOd9YFSG2uz47wcHO+aNEM0k76JFVBsed3DlkR04JMADonMLfjUjw5OSu9PJWDs1o28Xn2F+XjYlYeT9iRSVOXiSCngLB8vZcwFa1Zp7uhPD14HRKKtw34dmPZH8Q8= Received: by 10.66.242.5 with SMTP id p5mr1027871ugh.1193671332718; Mon, 29 Oct 2007 08:22:12 -0700 (PDT) Received: from ?172.24.32.184? ( [62.232.55.118]) by mx.google.com with ESMTPS id b23sm13253660ugd.2007.10.29.08.22.09 (version=SSLv3 cipher=RC4-MD5); Mon, 29 Oct 2007 08:22:09 -0700 (PDT) Message-ID: <4725FA9F.7050207@enterprisedb.com> Date: Mon, 29 Oct 2007 15:22:07 +0000 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.12 (X11/20070730) MIME-Version: 1.0 To: Nimesh Satam CC: pgsql-performance@postgresql.org, nimesh@zedo.com Subject: Re: Append Cost in query planners References: <965aa3ed0710280822x4d1ffc9dh74f67740fdcff5cb@mail.gmail.com> <4724ACE7.4090401@enterprisedb.com> <965aa3ed0710280950p7b931873w213e78f2b170176a@mail.gmail.com> <4724D34C.1000606@enterprisedb.com> <965aa3ed0710290409w1d7680fke7858fd8667d664c@mail.gmail.com> <4725C695.6010704@enterprisedb.com> <965aa3ed0710290455i4c746b83j38c7c49d1aa4b726@mail.gmail.com> In-Reply-To: <965aa3ed0710290455i4c746b83j38c7c49d1aa4b726@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/346 X-Sequence-Number: 27368 Nimesh Satam wrote: > Thanks for the information. join_collapse_limit = 1 is already set before > sending the query plan. I assume that was a typo, and you really set it to 10 or higher... > Will a index scan on metrics.netkey help in improving the performance what > other configuration parameters should we consider while opting for > partition? Whether it helps or not depends on many things, like the distribution of the data, but it's worth trying. I'd try that first, before worrying about config parameters. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com