Re: pgsql: Prevent invalidation of newly synced replication slots. - Mailing list pgsql-hackers

From Greg Burd
Subject Re: pgsql: Prevent invalidation of newly synced replication slots.
Date
Msg-id 54F8BC8B-6F9D-4B91-8B68-AA02B7643B94@burd.me
Whole thread Raw
In response to Re: pgsql: Prevent invalidation of newly synced replication slots.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Prevent invalidation of newly synced replication slots.
List pgsql-hackers
> On Jan 27, 2026, at 10:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
>> Robert Haas <robertmhaas@gmail.com> writes:
>>> 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.
>
> D'oh: hamerkop doesn't run any TAP tests, let alone ones that require
> --enable-injection-points.  So that success proves nothing.
>
> Our other Windows animals (drongo, fairywren, unicorn) seem to be
> configured with -Dtap_tests=enabled, but nothing about injection
> points, so they will also skip 046_checkpoint_logical_slot.
> Seems like a bit of a blind spot in the buildfarm.
>
> regards, tom lane
>


I'll see if I can update unicorn today to enable injection points to add some coverage on Win11/ARM64/MSVC.  No
promisesthat will be diagnostic at all, but it seems like a good idea. 


-Dinjection_points=true


-greg


pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: docs: warn about post-data-only schema dumps with parallel restore.
Next
From: Sami Imseih
Date:
Subject: Re: Flush some statistics within running transactions