Re: pgsql: Prevent invalidation of newly synced replication slots.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <akapila(at)postgresql(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Prevent invalidation of newly synced replication slots.
Date: 2026-01-27 14:59:04
Message-ID: CA+TgmobdVhO0ckZfsBZ0wqDO4qHVCwZZx8sf=EinafvUam-dsQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 27, 2026 at 12:56 AM Amit Kapila <akapila(at)postgresql(dot)org> wrote:
> Prevent invalidation of newly synced replication slots.

This commit has broken CI for me. On the "Windows - Server 2022, VS
2019 - Meson & ninja" build, the following shows up in
046_checkpoint_logical_slot_standby.log:

2026-01-27 13:44:44.421 GMT startup[5172] FATAL: could not rename
file "backup_label" to "backup_label.old": Permission denied

I imagine this is going to break CI for everybody else too, as well as cfbot.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2026-01-27 15:02:16 pgsql: pg_waldump: Remove file-level global WalSegSz.
Previous Message Bertrand Drouvot 2026-01-27 06:36:11 Re: failed NUMA pages inquiry status: Operation not permitted

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-01-27 15:11:12 Re: pgsql: Prevent invalidation of newly synced replication slots.
Previous Message Jelte Fennema-Nio 2026-01-27 14:48:55 Re: meson: Make test output much more useful on failure (both in CI and locally)