| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| Date: | 2026-01-28 18:09:35 |
| Message-ID: | 46DAB528-A3E8-455E-B1BA-370865490ABD@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
> On 28 Jan 2026, at 21:53, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> Andrey observed that the tests pass
> for him with a much longer timeout.
Unfortunately, I was wrong. The job "Windows - Server 2022, MinGW64 - Meson" which failed yesterday did not fail today.
But it did not succeed either. CirrusCI seems just did not run it. I do not understand why.
Anyway, I cannot prove that it is race condition. On a contrary, test fails on any big timeout (pg_ctl will bail out) deterministically.
Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Greg Burd | 2026-01-28 18:01:23 | Re: pgsql: Prevent invalidation of newly synced replication slots. |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Greg Burd | 2026-01-28 18:01:23 | Re: pgsql: Prevent invalidation of newly synced replication slots. |