Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dt6hS-0003rn-QP for pgsql-performance@arkaria.postgresql.org; Sat, 16 Sep 2017 06:35:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dsz3w-0007tF-LX for pgsql-performance@arkaria.postgresql.org; Fri, 15 Sep 2017 22:26:16 +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 1dsz3v-0007s4-IT for pgsql-performance@postgresql.org; Fri, 15 Sep 2017 22:26:15 +0000 Received: from mail-wr0-x233.google.com ([2a00:1450:400c:c0c::233]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dsz3s-0008Kn-7C for pgsql-performance@postgresql.org; Fri, 15 Sep 2017 22:26:14 +0000 Received: by mail-wr0-x233.google.com with SMTP id k20so2775135wre.4 for ; Fri, 15 Sep 2017 15:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=I48MhDGvRA9yQGP6bKym73onSHd30w8fr3jKJs9/t0w=; b=NdsEl3hqGf/8QaQKHSX/i5x5KQnfpfpQAu/hvLs07+ga+0zvx/dAW9QnNH1SEwKxa2 wNX6LPfeCewEtx9la4p1yUcCWjiY2JWPo8xMc0E5b7Cb31SvZz/bvZ0+2h5uWCIgbCEo Fd3/W0rS11j7IKxYld6w9Yst8ZKYhCIennoNZurwxf9CwdOEjTGJGPcBrNUpGqrSlap7 PU3sfAgnPonMOxxnNZlSeMMpmLnldDKq5ksKBgtKI4GaiHsI7yTjyIzKgRV6Nlssc4Vy Qf+At9f6CcDsrF6u2r0L++TOxBOc4qozUQE+gAzc6U5OHUGy239DEtlRi3juTuD08iQ7 kHGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=I48MhDGvRA9yQGP6bKym73onSHd30w8fr3jKJs9/t0w=; b=n9SWqiMBNWoNqKmFAUyJSDEkb/2iLkt8H/zyFjgqefzxtVhyluEbUqUbQeL8FpT5cf l2I0q5CIBLaZB1NobHJge/bhAyden94Lxe6JqKMVfS7yCO8Wbvj487bThQHwiBIytbrp fjJl84WQS32D8YR8TzHR3s0TxjZz11rx33q4GkqptfGg5WNhXNBLU21EznAqrX/59ebm IzKvLh9u5VpqevkIYDqF7JuDDrrsNUFH2lxaKFL81zy3UIUdt8Ts6wTpitWfnAwNnLPf BFek/k9eL5GPw8b68V1SRUgYGqPMnfr5rR6ULarhPDV/MZJ06q1U4s2BPGu1Hu3E8Xib vh3Q== X-Gm-Message-State: AHPjjUgKP+5WYoGwn5qBq+8T+D3ZLlQb2b/0jEbh5o9KKkyE3T0YNM48 vwck9zumc0KGQQ+5 X-Google-Smtp-Source: ADKCNb5MbwZkbTHJ7Pt4UQJxeGLGRgz+UXcMIYgMqNp5AsyjAsh/VKCjOZznNDgWz7sCXQ80dYf7OQ== X-Received: by 10.223.182.80 with SMTP id i16mr23566018wre.131.1505514370558; Fri, 15 Sep 2017 15:26:10 -0700 (PDT) Received: from [10.137.2.19] (ip-78-102-97-226.net.upcbroadband.cz. [78.102.97.226]) by smtp.gmail.com with ESMTPSA id l73sm3462040wma.24.2017.09.15.15.26.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Sep 2017 15:26:09 -0700 (PDT) Subject: Re: query of partitioned object doesnt use index in qa To: Tom Lane , Andres Freund Cc: pgsql-performance@postgresql.org, Mike Broers , David Rowley References: <3138.1505508143@sss.pgh.pa.us> <862584A2-724B-4F5A-976F-6164AE61BBE5@anarazel.de> <9414.1505513131@sss.pgh.pa.us> From: Tomas Vondra Message-ID: Date: Sat, 16 Sep 2017 00:26:06 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <9414.1505513131@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 09/16/2017 12:05 AM, Tom Lane wrote: > Andres Freund writes: >> I'm wondering if we should extend the new CREATE STATISTICS >> framework to be able to do that without requiring an index. > > I think that's already on the roadmap --- it's one of the reasons we > ended up with a SELECT-like syntax for CREATE STATISTICS. But it > didn't get done for v10. > Right. It's one of the things I'd like to be working on after getting in the more complex statistics types (MCV & histograms). > If we do look at that as a substitute for "make an expression index > just so you get some stats", it would be good to have a way to > specify that you only want the standard ANALYZE stats on that value > and not the extended ones. > Not sure I understand what you mean by "extended" - the statistics we collect for expression indexes, or the CREATE STATISTICS stuff? I assume the former, because if you don't want the latter then just don't create the statistics. Or am I missing something? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance