Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans)
Date
Msg-id CAH2-WzkYXSnM60ZNo-vQLxFoGzHLHFD0x=iPHF6VGxiZmWUuwQ@mail.gmail.com
Whole thread Raw
In response to Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Committed just now. Thanks again.

On Mon, Mar 3, 2025 at 4:01 PM Robert Haas <robertmhaas@gmail.com> wrote:
> On Thu, Feb 27, 2025 at 7:58 PM Peter Geoghegan <pg@bowt.ie> wrote:
> > It's easy to produce an example that makes intuitive sense. For
> > example, with skip scan that has a qual such as "WHERE a BETWEEN 1 and
> > 5 AND b = 12345", it is likely that EXPLAIN ANALYZE will show "Index
> > Searches: 5" -- one search per "a" value. Such an example might be
> > more useful than my original pgbench_accounts example.
> >
> > Do you think that that would help?
>
> Yes.

As you might have seen already, I added an example involving SAOPs to
"14.1.2. EXPLAIN ANALYZE". I have a TODO item about adding an
additional example involving skip scan immediately afterwards, as part
of the skip scan patch.

> > Perhaps a comment noting why the new counter lives in IndexScanDesc would help?
>
> +1.

Added a IndexScanDesc comment about this to the committed version.

--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: should num_custom_plans be reset after plan invalidation?
Next
From: Matthias van de Meent
Date:
Subject: Re: Hook for Selectivity Estimation in Query Planning