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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-27 15:11:12
Message-ID: 428236.1769526672@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 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.

Hmm, I wonder why the buildfarm seems fine with it ... I'm prepared
to believe a Windows-only problem, but at least hamerkop has run
since 851f664.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2026-01-27 15:49:39 Re: pgsql: Prevent invalidation of newly synced replication slots.
Previous Message Robert Haas 2026-01-27 15:02:16 pgsql: pg_waldump: Remove file-level global WalSegSz.

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-01-27 15:22:51 Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY
Previous Message Robert Haas 2026-01-27 14:59:04 Re: pgsql: Prevent invalidation of newly synced replication slots.