Feedback-ID: i0c21471d:Fastmail
MIME-Version: 1.0
Date: Fri, 17 Apr 2026 23:19:24 -0300
From: "Euler Taveira" <euler@eulerto.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>, "Michael Paquier" <michael@paquier.xyz>
Cc: "Robert Haas" <robertmhaas@gmail.com>,
 "Andres Freund" <andres@anarazel.de>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
Message-Id: <a8e80680-c4a6-4125-8500-ab31924f8d85@app.fastmail.com>
In-Reply-To: <3311981.1776462484@sss.pgh.pa.us>
References: <3ydjipcr7kbss57nvi67noplncqhesl5eyb6wgol4ccjxynspv@yatlykpribmm>
 <CA+TgmoZJzNQ_ATdOi+WUZwc=SO5GjGKBbEBrMyLCmDZpkJ1D0Q@mail.gmail.com>
 <aeKpFoT5qONuZ-AM@paquier.xyz> <3311981.1776462484@sss.pgh.pa.us>
Subject: Re: Heads Up: cirrus-ci is shutting down June 1st
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a8e80680-c4a6-4125-8500-ab31924f8d85%40app.fastmail.com>
Precedence: bulk

On Fri, Apr 17, 2026, at 6:48 PM, Tom Lane wrote:
>
> I think running a test promptly after a new patch submission is
> useful, even for small patches.  I agree that the periodic re-tests
> for bit-rot could be scaled back a lot.
>

That's my opinion too. This is particularly important for first-time
contributors that may not know about the Postgres development process. For
regular contributors, I expect that they have a CI setup and submit a new
version only after the patch passes CI in its own repository.

I'm not sure about restricting the CI runs to small patches. Although it is a
minority, there are small patches that has a big potential to break things.
Maybe an alternative to small and/or high-frequency patches is to not run them
automatically but have a mechanism to trigger them manually once detected. The
author or even one of the reviewers can trigger it.


-- 
Euler Taveira
EDB   https://www.enterprisedb.com/