Re: improve transparency of bitmap-only heap scans - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: improve transparency of bitmap-only heap scans
Date
Msg-id CAA4eK1+fw4GnHk1KrD8Q3no7zcRV+tvkN4HZGW2J1e_zo-=k=g@mail.gmail.com
Whole thread Raw
In response to Re: improve transparency of bitmap-only heap scans  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: improve transparency of bitmap-only heap scans  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
On Wed, Mar 25, 2020 at 12:44 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I took a quick look through this patch.  While I see nothing to complain
> about implementation-wise, I'm a bit befuddled as to why we need this
> reporting when there is no comparable data provided for regular index-only
> scans.  Over there, you just get "Heap Fetches: n", and the existing
> counts for bitmap scans seem to cover the same territory.
>

Isn't deducing similar information ("Skipped Heap Fetches: n") there
is a bit easier than it is here?

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Dave Sharpe
Date:
Subject: [PATCH] Fix CommitTransactionCommand() to CallXactCallbacks() inTBLOCK_ABORT_END
Next
From: Thomas Munro
Date:
Subject: Re: Collation versions on Windows (help wanted, apply within)