Re: EXPLAIN: showing ReadStream / prefetch stats

Melanie Plageman <melanieplageman@gmail.com>

From: Melanie Plageman <melanieplageman@gmail.com>

To: Tomas Vondra <tomas@vondra.me>

Cc: Andres Freund <andres@anarazel.de>, Lukas Fittl <lukas@fittl.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-04-06T20:33:16Z

Lists: pgsql-hackers

Attachments

v10-0001-Assert-no-duplicate-keys-in-shm_toc_insert.patch (text/x-patch) patch v10-0001
v10-0002-Allocate-separate-DSM-chunk-for-parallel-Index-O.patch (text/x-patch) patch v10-0002

On Mon, Apr 6, 2026 at 12:50 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> I cleaned up the first patch in the set that refactors index-only and
> index scan to use this pattern and realized that I wasn't sure what to
> do about the duplication between index-only and index scans for these
> functions.

I changed my mind about the duplication: I think it's fine because
there just aren't that many lines of code. Attached v10 has a
preparatory commit that adds an assert-only check to shm_toc_insert()
to make sure the key hasn't already been inserted. I thought it would
be helpful since many of the magic numbers for parallel executor
communication are spread around.

- Melanie

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

bufmgr: Return whether WaitReadBuffers() needed to wait
- 513374a47a71 19 (unreleased) landed