| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| 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-23 17:37:20 |
| Message-ID: | CAAKRu_YEW7k5uAc05oyUu3ggoxehGy5En87ToUiDJWxAeSjPtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Mar 23, 2025 at 1:02 PM Andrey Borodin <x4mmm(at)yandex-team(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2025-03-23 18:00:01 | Re: Regression test postgres_fdw might fail due to autovacuum |
| Previous Message | Melanie Plageman | 2025-03-23 17:30:07 | Re: Regression test postgres_fdw might fail due to autovacuum |