Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1jRel5-0005B9-SG
	for pgsql-performance@arkaria.postgresql.org; Thu, 23 Apr 2020 16:31:27 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1jRel4-0004gP-Os
	for pgsql-performance@arkaria.postgresql.org; Thu, 23 Apr 2020 16:31:26 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jRel4-0004fw-Hu
	for pgsql-performance@lists.postgresql.org; Thu, 23 Apr 2020 16:31:26 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jRel0-0004D6-MP
	for pgsql-performance@lists.postgresql.org; Thu, 23 Apr 2020 16:31:25 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03NGVGq8014951;
	Thu, 23 Apr 2020 12:31:16 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Lewis <mlewis@entrata.com>
cc: "David G. Johnston" <david.g.johnston@gmail.com>,
        Thomas Kellerer <shammat@gmx.net>,
        "pgsql-performance@lists.postgresql.org"
 <pgsql-performance@lists.postgresql.org>
Subject: Re: PostgreSQL does not choose my indexes well
In-reply-to: 
 <CAHOFxGrf_CsHgfQKnQp18G0_1CC6aQCbQ5Rz5JuD2u_rSAQWDg@mail.gmail.com>
References: <35dc90d6-e0c2-13b8-3184-e3db5d854a78@gmail.com>
 <1bb37a19-77f6-8c49-073e-ed6251c98583@gmx.net>
 <CAKFQuwY9twbudMDvmuo+9Mjy0y-cJcvzPazD07-oB+WV1qOMnA@mail.gmail.com>
 <4315.1587655779@sss.pgh.pa.us>
 <CAHOFxGrf_CsHgfQKnQp18G0_1CC6aQCbQ5Rz5JuD2u_rSAQWDg@mail.gmail.com>
Comments: In-reply-to Michael Lewis <mlewis@entrata.com>
	message dated "Thu, 23 Apr 2020 10:20:41 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14949.1587659476.1@sss.pgh.pa.us>
Date: Thu, 23 Apr 2020 12:31:16 -0400
Message-ID: <14950.1587659476@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Precedence: bulk

Michael Lewis <mlewis@entrata.com> writes:
>> "unless the table is mostly marked all-visible"

> Is that taken into account during planning when evaluating index scan vs
> sequential scan?

It is, although the planner's estimate is based on what the last ANALYZE
saw, which might be out-of-date.

			regards, tom lane