Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1inNim-0002uq-JB for pgsql-performance@arkaria.postgresql.org; Fri, 03 Jan 2020 14:14:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1inNil-0001we-5m for pgsql-performance@arkaria.postgresql.org; Fri, 03 Jan 2020 14:14:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1inNik-0001wW-Or for pgsql-performance@lists.postgresql.org; Fri, 03 Jan 2020 14:14:34 +0000 Received: from mail-yw1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1inNih-0002MA-SY for pgsql-performance@postgresql.org; Fri, 03 Jan 2020 14:14:34 +0000 Received: by mail-yw1-xc2e.google.com with SMTP id h126so18552222ywc.6 for ; Fri, 03 Jan 2020 06:14:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version:content-disposition :user-agent; bh=X1wfz729HDU8i8TokwXbpeGwecOesAL3YOzqPj3VmGU=; b=KP+NOiUwrehRtyKO/K8+D5gnH5A6kuNahzu6wlazX0hfKz/Z74WeShAMqT8myew8c0 Orlf4rkxE1F16tWzBdcZd88me8nqxwyys0o3OfIUGzNcFOsLye/5PBtgEvX4REYIpagx +C98KgKP0bd0RX8DlPOVeygjlPFHrM3oQgreLAHc8MH49TkHWjlEgNtX0B5Dlk/A36FG ocp2nOo+IeyxvQTVfkRVNuFHmaY1dQd7wALjnpY9ZmX1T7gGSev0+a3lb6Rz1A4tE7W3 qdc4OwRqUNIi+NsN+zfHD04QWsraqmQpoXB4a4IKG6KM66nkpnSevDavVfUMi9yxUWR1 Cd+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=X1wfz729HDU8i8TokwXbpeGwecOesAL3YOzqPj3VmGU=; b=l2bAwDA1zCz60sArR8K3mvV7GgnHa2OZHHu+wC4dWAX8LS0AwCIjR5JBNpk11/r0W8 ejaf2KotSRkLxwJ4RnPFiCo8tS+dLPjiSh8A5maRrh7Wd+iv5UsbFDZjCPhmDY0q+P+k QxwnI5AQdlK/c0lRpU5oorPiS9AX2tSzEZuayH2c3+rtCsluypUn5zOMv3Z3ZnYj/HZ7 FPZwaM9Si5ixme4B7x6Gs6xj4Fwb6xIvVSkD9GLPawwLs/VDw7dUONLR+gfLLGUGFwyo fBwl84xXezjNHtNE8PsjKjoQyHTi7IrIDlO2hHF9VX4NKT2bE6U9jVrwzw3bsoaJ4uvI 6KKA== X-Gm-Message-State: APjAAAU/mT7luq0fp4yWbF0VjdbhwmJNrSD8IV+lkCOQfPPMXCg1j8bE 906rB10IjJwVns3XGEBm/xOhZAdfm1E= X-Google-Smtp-Source: APXvYqz3R3YYngOtYxmLyHAa4ifdOBygJ5fq+e/IVE2uByEW9gT5DCH1wvH5tC3GAWE2kx5JMja82A== X-Received: by 2002:a81:b654:: with SMTP id h20mr62223407ywk.272.1578060869649; Fri, 03 Jan 2020 06:14:29 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id y17sm23758538ywd.23.2020.01.03.06.14.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Jan 2020 06:14:28 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id A57FB8008C4; Fri, 3 Jan 2020 08:14:27 -0600 (CST) Date: Fri, 3 Jan 2020 08:14:27 -0600 From: Justin Pryzby To: pgsql-performance@postgresql.org Subject: distinguish index cost component from table component Message-ID: <20200103141427.GK12066@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Is it possible to tell what component of the cost estimate of an index scan is from the index reads vs heap ? It would help to be able to set enable_bitmapscan=FORCE (to make all index scans go through a bitmap). Adding OR conditions can sometimes do this. That includes cost of bitmap manipulation, but it's good enough for me. Or maybe explain should report it.