On Thu, Apr 10, 2025 at 11:15 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> The new streaming BHS isn't just issuing probabilistic hints about
> future access obtained from a second iterator. It has just one shared
> iterator connected up to the workers' ReadStreams. Each worker pulls
> a disjoint set of blocks out of its stream, possibly running a bunch
> of IOs in the background as required.
It feels to me like the problem here is that the shared iterator is
connected to unshared read-streams. If you make a shared read-stream
object and connect the shared iterator to that instead, does that
solve this whole problem, or is there more to it?
--
Robert Haas
EDB: http://www.enterprisedb.com