Date: Mon, 11 May 2020 20:22:46 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200512002246.GJ4666@momjian.us>
References: <20200505031600.GB21752@momjian.us>
 <CAA4eK1+tOd6vTXBjUyjEQF+NALdoX8d-EZu5HEs_nxZ-huX2Hw@mail.gmail.com>
 <CAA4eK1+DDmycMNy9VQH8dFcPnkF5j8MNWVHL4yWNZ_0BL8HF2Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAA4eK1+DDmycMNy9VQH8dFcPnkF5j8MNWVHL4yWNZ_0BL8HF2Q@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

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

Yes.

> allow index-only scans to skip "Heap Fetches" in more cases.

Uh, by definition an index-only scan only scans the index, not the heap,
right?  It is true there are fewer heap fetches, but fewer heap features
I thought mean more index-only scans.

-- 
  Bruce Momjian  <bruce@momjian.us>        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 +