Re: Support tid range scan in parallel?

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Cary Huang <cary(dot)huang(at)highgo(dot)ca>
Cc: Junwang Zhao <zhjwpku(at)gmail(dot)com>, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support tid range scan in parallel?
Date: 2025-11-27 05:48:11
Message-ID: CAApHDvqALm+k7FyfdQdCw1yF_8HojvR61YRrNhwRQPE=zSmnQA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 27 Nov 2025 at 14:07, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I went over this again today and only made a few whitespace
> adjustments in the tests. I've now pushed the resulting patch.

This seems to have caused issues on skink [1] under Valgrind. The
problem seems to be that initscan() does not always initialise
rs_startblock. I'm now trying to figure out if there's some reason for
that, or if that's been overlooked at some point.

David

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2025-11-27%2002%3A17%3A35

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2025-11-27 05:48:56 Re: pgsql: doc: Fix incorrect wording for --file in pg_dump
Previous Message Shlok Kyal 2025-11-27 05:38:00 Re: How can end users know the cause of LR slot sync delays?