Re: Using read_stream in index vacuum

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: Using read_stream in index vacuum
Date: 2025-03-19 09:25:57
Message-ID: 65F792CD-1B54-4260-AE49-121EFB717363@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Mar 2025, at 23:21, Melanie Plageman <melanieplageman(at)gmail(dot)com> wrote:
>
> I actually think you could do the test with one injection point and
> just wait on it twice

I was not sure we can safely wake up on injection point and stop and the same point on next iteration.
But, apparently, it is safe, due to wait_counts in InjectionPointSharedState.

So, yes, your change to the test seems correct to me. We can do the test with just one injection point.

Best regards, Andrey Borodin.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-03-19 09:44:48 Re: Adding a '--clean-publisher-objects' option to 'pg_createsubscriber' utility.
Previous Message Ilia Evdokimov 2025-03-19 09:16:01 Re: Add missing tab completion for VACUUM and ANALYZE with ONLY option