| 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-06 18:54:17 |
| Message-ID: | CA+Tgmoa+ZHivezQgVGvU7xfD2zr3n8L-Z0Rw41vxszeL5ThcQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 6, 2025 at 1:17 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> The immediate problem is that when the parallel leader doesn't
> participate, there is no valid IndexScanDescData in planstate to work
> off of. There isn't an obvious way to get to shared memory from the
> leader process, since that all goes through the
> IndexScanDescData.parallel_scan -- there is nothing that points to
> shared memory in any of the relevant planstate structs (namely
> IndexScanState, IndexOnlyScanState, and BitmapIndexScanState). I was
> hoping that you'd be able to provide some guidance on how best to fix
> this.
Hmm, it seems weird that you can't get a hold of that structure to me.
Why can't you just go find it in the DSM?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2025-03-06 18:58:04 | Re: Showing primitive index scan count in EXPLAIN ANALYZE (for skip scan and SAOP scans) |
| Previous Message | Robert Haas | 2025-03-06 18:52:42 | Re: what's going on with lapwing? |