Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V3u41-0007rX-GO for pgsql-performance@arkaria.postgresql.org; Mon, 29 Jul 2013 20:29:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1V3u40-0003CM-Uq for pgsql-performance@arkaria.postgresql.org; Mon, 29 Jul 2013 20:29:04 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V3u3z-0003AV-2F for pgsql-performance@postgresql.org; Mon, 29 Jul 2013 20:29:03 +0000 Received: from nm36-vm6.bullet.mail.bf1.yahoo.com ([72.30.238.142]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V3u3u-00053H-N6 for pgsql-performance@postgresql.org; Mon, 29 Jul 2013 20:29:02 +0000 Received: from [66.196.81.171] by nm36.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jul 2013 20:28:57 -0000 Received: from [98.139.212.230] by tm17.bullet.mail.bf1.yahoo.com with NNFMP; 29 Jul 2013 20:28:57 -0000 Received: from [127.0.0.1] by omp1039.mail.bf1.yahoo.com with NNFMP; 29 Jul 2013 20:28:57 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 360080.32519.bm@omp1039.mail.bf1.yahoo.com Received: (qmail 39179 invoked by uid 60001); 29 Jul 2013 20:28:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1375129737; bh=XKUzDQXDDYhj6naeWQMglwOnC2vc4qTssKwYlOkWQsc=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=o0x5nNng3UGc6Btc+0UtV467sXO4zDk0iYa8uuMCyJgVgeYd+OaVsxUyMmn0kVyej8/G5mtVTIBPIDDoG30a2v3w5nO8Cy1jC0uib6VW+4sdFx8Gyl1BO/2O8QN2vll5k732b9KUaA5cG5djlfho2ZfAonm6GtesfHE/zK7KKm8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AEHiBDZytWwotFkbTUlTEHiG58dWeYiC8qQ9ZbfPwLILEhAz3EnwTBzCdJoAkGpnduxRlf7xQL3Tm0wp9Zt9sOieep5Y+rR3nv99Oy9Ll35O5fRr888sIMkIdRNZED4/cMuMvKs15Tuv45hBr0F1zUkvj0OLK6CR1uCIVgUfcR0=; X-YMail-OSG: nLdwK8AVM1muhiKkyviEnmEGGd_2zlj.XcW2lbGitLiKU7D d75308Okl0ry4SkrTtwAp9UPTF_Ic2J4JfSBAS5s1Hhj2AE2P6oQblSZnVrR R4ydjbPBMb6rZnyNzRHAxm9iqhspxjzPGkdgJJbCGiwCOpp40sHBDsfaujrl p0PcxMzdTzXUsYJuWSyaSCQ3zVGNISDVX_JfJ9W8oqLGyxT71dV6xQe7OlBc QrSoTytJs7E_CIBN4k9u9hIhPnIRG93mc1QyL7TP_XKC84KI2OVa7RjZze60 0jOeE_U5uB8o61YKNeeH6rfQZf3YV2O9PzZNnM9vjB5KAwAaSwxyV0oibPuV BtvmaBE7wvs9.b_JkqAaOd1OXa4gEU_ujc8CntIerVGZpp2J5k4eZpNgq7M9 wayaU.x0QO8hUs9rvI9arRBy1q9k4xjKpwtp_45sC73HAc9_zAil4lUyr56I DJws_Gl48Hptkbr6ESOIdSdElQr1DO0JbHonDE88sXO24NsJicTtxFZchzOF 3jBC9C1H95nqH5sHHTJ1_Hliez.Vf0PAtHpKnX6sRaH0ieMwqZHN6qD60Kb. ynIKNBmZWibI6redQjwJcIQCFynTAlbhW35NX Received: from [76.255.18.237] by web162901.mail.bf1.yahoo.com via HTTP; Mon, 29 Jul 2013 13:28:56 PDT X-Rocket-MIMEInfo: 002.001, U3RlZmFuIEtlbGxlciA8c2ZrZWxsZXJAZ21haWwuY29tPiB3cm90ZToKCj4gRmluYWxseSwgc2V0dGluZyByYW5kb21fcGFnZV9jb3N0IHRvIDEgaGVscHMgYWxzbyAtIGJ1dCBJIGRvbid0Cj4gbGlrZSB0aGlzIHNldHRpbmcgbmVpdGhlci4KCldlbGwsIHlvdSBzaG91bGQgbGVhcm4gdG8gbGlrZSB3aGljaGV2ZXIgc2V0dGluZ3MgYmVzdCBtb2RlbCB5b3VyCmFjdHVhbCBjb3N0cyBnaXZlbiB5b3VyIGxldmVsIG9mIGNhY2hpbmcgYW5kIHlvdXIgd29ya2xvYWQuwqAgOy0pCkZXSVcsIEkgaGF2ZSBmb3VuZCABMAEBAQE- X-Mailer: YahooMailWebService/0.8.151.566 References: Message-ID: <1375129736.38828.YahooMailNeo@web162901.mail.bf1.yahoo.com> Date: Mon, 29 Jul 2013 13:28:56 -0700 (PDT) From: Kevin Grittner Reply-To: Kevin Grittner Subject: Re: FTS performance issue - planner problem identified (but only partially resolved) To: Stefan Keller , "pgsql-performance@postgresql.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 0.7 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Stefan Keller wrote: > Finally, setting random_page_cost to 1 helps also - but I don't > like this setting neither. Well, you should learn to like whichever settings best model your actual costs given your level of caching and your workload.=A0 ;-) FWIW, I have found page costs less volatile and easier to tune with cpu_tuple_cost increased.=A0 I just always start by bumping that to 0.03. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance