Re: Using read_stream in index vacuum - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: Using read_stream in index vacuum
Date
Msg-id CAAKRu_YEW7k5uAc05oyUu3ggoxehGy5En87ToUiDJWxAeSjPtA@mail.gmail.com
Whole thread Raw
In response to Re: Using read_stream in index vacuum  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
On Sun, Mar 23, 2025 at 1:02 PM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
> There's a BF failure with just these changes [0]. But IMO it's unrelated.
> There are 2 failed tests:
> 1. 'activeslot slot invalidation is logged with vacuum on pg_authid' is very similar to what is discussed here [1]
> 2. '+ERROR: tuple concurrently deleted' in injection_points/isolation seems to be discussed here [2]

Yep, I saw the recovery/035_standby_logical_decoding skink failure and
concluded it was caused by a pre-existing issue that is already being
discussed. I hadn't yet investigated the injection point isolation
test failure. So, it is good to know it seems like it is a known
issue. Thanks for being on the lookout.

- Melanie



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Regression test postgres_fdw might fail due to autovacuum
Next
From: Alexander Lakhin
Date:
Subject: Re: Regression test postgres_fdw might fail due to autovacuum