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-05 14:37:05 |
Message-ID: | CAH2-WzkYXSnM60ZNo-vQLxFoGzHLHFD0x=iPHF6VGxiZmWUuwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Committed just now. Thanks again.
On Mon, Mar 3, 2025 at 4:01 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 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.
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
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2025-03-05 14:37:37 | Re: Hook for Selectivity Estimation in Query Planning |
Previous Message | Andrew Dunstan | 2025-03-05 14:33:35 | Announcing Release 19.1 of the PostgreSQL Buildfarm client |