Re: improve transparency of bitmap-only heap scans

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Alexey Bashtanov <bashtanov(at)imap(dot)cc>
Cc: Emre Hasegeli <emre(at)hasegeli(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improve transparency of bitmap-only heap scans
Date: 2020-02-07 21:35:19
Message-ID: 20200207213519.mjgcvnpz6gn7pkyd@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 07, 2020 at 03:22:12PM +0000, Alexey Bashtanov wrote:
>Hello,
>
>>It took me a while to figure out what those names mean. "unfetched",
>>as you call it on the code, may be more descriptive than "avoided" for
>>the new label. However I think the other two are more confusing. It
>>may be a good idea to change them together with this.
>It'll be sad if this patch is forgotten only because of the words choice.
>I've changed it all to "unfetched" for at least not to call the same
>thing differently
>in the code and in the output, and also rebased it and fit in 80 lines
>width limit.
>

I kinda suspect one of the ressons why this got so little attention is
that it was never added to any CF.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-02-07 21:56:27 Draft release notes are up for review
Previous Message Thomas Munro 2020-02-07 21:15:18 Re: Reducing WaitEventSet syscall churn