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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Burd <greg(at)burd(dot)me>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 17:11:23
Message-ID: CA+TgmoZFs8Xqf4J5fEgXiZcpH4cK0jEygB7s13riPyGKB-n17w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 27, 2026 at 11:53 AM Greg Burd <greg(at)burd(dot)me> wrote:
> I'll see if I can update unicorn today to enable injection points to add some coverage on Win11/ARM64/MSVC. No promises that will be diagnostic at all, but it seems like a good idea.
> -Dinjection_points=true

Sounds good!

Thanks,

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2026-01-27 17:42:51 Re: pgsql: Prevent invalidation of newly synced replication slots.
Previous Message Greg Burd 2026-01-27 16:53:38 Re: pgsql: Prevent invalidation of newly synced replication slots.

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2026-01-27 17:21:11 Re: Add SECURITY_INVOKER_VIEWS option to CREATE DATABASE
Previous Message Andres Freund 2026-01-27 17:02:59 Re: unnecessary executor overheads around seqscans