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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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-01 22:39:56
Message-ID: CAH2-Wz=zzD+752xD8NjVfdxh6c_vRdhWhwRHSw4qXOt=quk=vg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 27, 2025 at 7:57 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Thu, Feb 27, 2025 at 3:42 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > Good documentation could help.

Attached revision adds an example that shows how "Index Searches: N"
can vary. This appears in "14.1.2. EXPLAIN ANALYZE".

Other changes in this revision:

* Improved commit message.

* We now consistently show "Index Searches: N" after all other scan
related output, so that it will reliably appear immediately before the
"Buffers: " line.

This seemed slightly better, since it is often useful to consider
these two numbers together.

My current plan is to commit this patch on Wednesday or Thursday,
barring any objections.

Thanks
--
Peter Geoghegan

Attachment Content-Type Size
0001-Show-index-search-count-in-EXPLAIN-ANALYZE.patch application/octet-stream 55.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-03-01 23:54:21 Re: bug when apply fast default mechanism for adding new column over domain with default value
Previous Message Ed Behn 2025-03-01 22:25:19 Re: access numeric data in module