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 ) id 1jYJND-0004BQ-En for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 01:06:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jYJNC-000517-5l for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 01:06:18 +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 ) id 1jYJNB-00050q-UA for pgsql-hackers@lists.postgresql.org; Tue, 12 May 2020 01:06:17 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYJN9-0001SF-GO for pgsql-hackers@postgresql.org; Tue, 12 May 2020 01:06:16 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jYJN8-0006to-0x; Mon, 11 May 2020 21:06:14 -0400 Date: Mon, 11 May 2020 21:06:14 -0400 From: Bruce Momjian To: Justin Pryzby Cc: Amit Kapila , PostgreSQL-development Subject: Re: PG 13 release notes, first draft Message-ID: <20200512010614.GO4666@momjian.us> References: <20200505031600.GB21752@momjian.us> <20200512004155.GP18456@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200512004155.GP18456@telsasoft.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, May 11, 2020 at 07:41:55PM -0500, Justin Pryzby wrote: > On Mon, May 11, 2020 at 10:52:41AM +0530, Amit Kapila wrote: > > One more observation: > > > > Allow inserts to trigger autovacuum activity (Laurenz Albe, Darafei > > Praliaskouski) > > This new behavior allows pages to be set as all-visible, which then > > allows index-only scans, ... > > > The above sentence sounds to mean that this feature allows index-only > > scans in more number of cases after this feature. Is that what you > > intend to say? If so, is that correct? Because I think this will > > allow index-only scans to skip "Heap Fetches" in more cases. > > I think what you mean is that the autovacuum feature, in addition to > encouraging the *planner* to choose an indexonly scan, will *also* allow (at > execution time) fewer heap fetches for a plan which would have > already/previously used IOS. Right ? So maybe it should say "allows OR > IMPROVES index-only scans" or "allows plans which use IOS to run more > efficiently". Yes, I see your point now. New text is: This new behavior reduces the work necessary when the table needs to be frozen and allows pages to be set as all-visible. All-visible pages allow index-only scans to access fewer heap rows. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +