Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans)
Date: 2025-03-03 21:01:11
Message-ID: CA+TgmoYVaP0h44EbHZMGNe8QJ999hUhRj7XLsXnvVk8Y7vBh9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 27, 2025 at 7:58 PM Peter Geoghegan <pg(at)bowt(dot)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.

> It is unique right now, but perhaps only because this is the first
> piece of instrumentation that:

Yeah, possible.

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

+1.

> I do get that. I hope that you don't think that I've failed to take
> your feedback on board.

To the contrary, I appreciate you taking the time to listen to my opinion.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-03-03 21:49:09 Re: Ubsan complaint on kestrel
Previous Message Robert Haas 2025-03-03 20:52:30 Re: what's going on with lapwing?