Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1akGEt-0008Hn-LC for pgsql-performance@arkaria.postgresql.org; Sun, 27 Mar 2016 19:20:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1akGEs-0007Ch-B3 for pgsql-performance@arkaria.postgresql.org; Sun, 27 Mar 2016 19:20:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1akGEq-00079Y-Ul for pgsql-performance@postgresql.org; Sun, 27 Mar 2016 19:20:41 +0000 Received: from mail-lb0-x235.google.com ([2a00:1450:4010:c04::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1akGEo-00011X-Ej for pgsql-performance@postgresql.org; Sun, 27 Mar 2016 19:20:39 +0000 Received: by mail-lb0-x235.google.com with SMTP id bc4so71585872lbc.2 for ; Sun, 27 Mar 2016 12:20:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=JEH/DLWquu+T0sCde29djlE8nOfe+kiw+or6XoujXt4=; b=aHGJQjl+tHUuGwL1gArXlxbwrqPKShYB/vqqtys5t3iUsKLQmGT/lx3oMkTxX9K+aO nIme4NZW5/Xn+NQAKA+I++h8aPEbqy+rcqBH9lKyDxWqwUqr5X9oxVkD71V4dGkUPIpk Emk1ohqWkS8NUhD2ASXTEonB+B1K+MoHKL4WDvEOZ5iQ5vicw2huTLgXhCsGva859Nyi PxpfLvrv4eoMMjtajUJ3M9yC/2rWSy0VEgNlrot5b/jm/g0PEX/mzNrv8aiQIUqOEk/8 +uwd95LNHIpmV77EBQ7e+0Wy+yR8Y9cavC7f75NfLRJmfqGnK7qplq+4fjiAR/fm1/4x ZrrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=JEH/DLWquu+T0sCde29djlE8nOfe+kiw+or6XoujXt4=; b=W7iJJHIh9yJlsW9S9z34ewvM0GZ+Y/hzKo8poO9ldcvrQSDlcvKPIrmsC9rdjd4+JC 2Q6FYDgvj6O8Ux/jaG8qks8QrOPtoYWIyKEl/3ySKftB+UfFmKgL02OuMsHJW1rjduna S6XX2YCcBefXoe9u7jhfS+vfzTJVLCHH46kHuUjKe6GohmTSaAifQnqOeP8lDaB6qJQQ z/aJDXp2zHfSkFop4rbq3whqvwWrhMqpf9P/fc3UjtWEL98tAJAoF+HrE61kGQjdufYn V2ZpLNLyjw3JgE7Ab/HUbr3/WXoW5jj37AtYYxQqD/UpvhMuwfo9IQ7IfwHtmdxb6DRm PNiQ== X-Gm-Message-State: AD7BkJJsN+MV98ryXqEpoCbFiUMcunvrq3DFt13DDgREMwht9Ytj8Rdlfgs2bFCNolCb5OEe22NX+48Ec1LojQ== MIME-Version: 1.0 X-Received: by 10.112.163.102 with SMTP id yh6mr8531601lbb.4.1459106436625; Sun, 27 Mar 2016 12:20:36 -0700 (PDT) Received: by 10.25.145.5 with HTTP; Sun, 27 Mar 2016 12:20:36 -0700 (PDT) In-Reply-To: References: <20160326141346.GA32059@tux> Date: Sun, 27 Mar 2016 12:20:36 -0700 Message-ID: Subject: Re: Query not using Index From: Jeff Janes To: Wei Shan Cc: Andreas Kretschmer , "pgsql-performance@postgresql.org list" Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.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 On Sun, Mar 27, 2016 at 9:12 AM, Wei Shan wrote: > Hi Andreas, > > The tablespace is not on SSD although I intend to do it within the next > week. I actually tried reducing the random_page_cost to 0.2 but it doesn't > help. Setting random_page_cost to less than seq_page_cost is nonsensical. You could try to increase cpu_tuple_cost to 0.015 or 0.02 Cheers, Jeff -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance