Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTEkH-0006qN-KB for pgsql-performance@arkaria.postgresql.org; Fri, 19 Apr 2013 17:05:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UTEkH-0005jP-4L for pgsql-performance@arkaria.postgresql.org; Fri, 19 Apr 2013 17:05:09 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTEkG-0005hm-5T for pgsql-performance@postgresql.org; Fri, 19 Apr 2013 17:05:08 +0000 Received: from outbound.afilias.info ([66.199.183.4]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTEkC-0000GC-SH for pgsql-performance@postgresql.org; Fri, 19 Apr 2013 17:05:07 +0000 Received: from ms5.on1.afilias-ops.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtp (Exim 4.69) (envelope-from ) id 1UTEjz-0002mG-5w for pgsql-performance@postgresql.org; Fri, 19 Apr 2013 17:04:51 +0000 Received: from mail-fa0-f72.google.com ([209.85.161.72]) by smtp.afilias.info with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1UTEjz-00043D-5U for pgsql-performance@postgresql.org; Fri, 19 Apr 2013 17:04:51 +0000 Received: by mail-fa0-f72.google.com with SMTP id t1so6156114fae.7 for ; Fri, 19 Apr 2013 10:04:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=WyQFo0la3uR24nsJgVxcKpSrapNC1rlVm8yenv+t1sQ=; b=bDlgkrT8AR4TbMgj13fb0FSqGizjAldRZKbPjXLp3R1e6YDRJfRjEFMqZimUKRlskO PASYLQ9N2QMnb+Rm/OCZDRJ+z54Ns2ONBLvNLJFxMcGk8FZ5LCR95lEInSCYn8ZQwsAS sGCsIEPbjMpVbp20ffSM4JX+pIT14+0W/MjYJdwsY7pjy3pMZCBOKjBr7D1gx6+gdOMm YXJtCQEw2JK7L+cSDsKEOFnOzgDLTLu43zO7BuVvaxXUxf6TFTcit7DO96TsnDm8Mw01 JxUxLoCN/isVmv0DUQ4urUIRwHvNIZqX1MpRCbPWG/0H++SmaitRc6S1EBFGgtQTAzqi zDtA== X-Received: by 10.194.109.136 with SMTP id hs8mr27479220wjb.8.1366391085621; Fri, 19 Apr 2013 10:04:45 -0700 (PDT) X-Received: by 10.194.109.136 with SMTP id hs8mr27479211wjb.8.1366391085544; Fri, 19 Apr 2013 10:04:45 -0700 (PDT) Received: from [192.168.1.5] ([64.231.27.210]) by mx.google.com with ESMTPS id s2sm4764630wib.4.2013.04.19.10.04.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Apr 2013 10:04:44 -0700 (PDT) Message-ID: <51717928.2010602@ca.afilias.info> Date: Fri, 19 Apr 2013 13:04:40 -0400 From: Steve Singer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: Jeff Janes CC: "pgsql-performance@postgresql.org" Subject: Re: slow bitmap heap scans on pg 9.2 References: <51656E03.7000701@ca.afilias.info> <5165FBA1.90704@ca.afilias.info> <5166C69B.1010505@ca.afilias.info> <51698452.1050202@ca.afilias.info> <516B4492.7090204@ca.afilias.info> In-Reply-To: <516B4492.7090204@ca.afilias.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQmvU5AxEOX8vvrfQaYfi17zoFAUvQgNV+WIw+Dy8nhDNadIzD8rny2cQ3Py7S54CKZY9NTUKnZfFqqTsGZ3vNDFO8RRdoRlHEWU9FaQkHmyuJwFwPRWiB+PmNg1rIhvjcLuuTxWXX5++w1tq7uk2q4vXVPsQlOdCT1PObgT765qZFbBzbQ= X-Pg-Spam-Score: -2.6 (--) 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 On 13-04-14 08:06 PM, Steve Singer wrote: > On 13-04-13 04:54 PM, Jeff Janes wrote: >> >> If you are trying to make your own private copy of 9.2, then removing >> the fudge factor altogether is probably the way to go. But if you want >> to help improve future versions, you probably need to test with the most >> up-to-date dev version. > > I will do that in a few days. I don't have enough disk space on this > dev server to have a 9.2 datadir and a 9.3 one for this database. Once > I have a solution that I can use with 9.2 firmed up I can upgrade the > datadir to 9.3 and test this. I am hoping I can get a set of partial > indexes that will give good results with an unmodified 9.2, so far that > looks promising but I still have more cases to verify (these indexes > take a while to build). > I've run these queries against a recent master/9.3 and the planner is picking the nested-loop plan for using the full index. This is with random_page_cost=2. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance