Re: PG vs LLVM 12 on seawasp, next round - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG vs LLVM 12 on seawasp, next round
Date
Msg-id 1698296.1611547578@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG vs LLVM 12 on seawasp, next round  (Noah Misch <noah@leadboat.com>)
Responses Re: PG vs LLVM 12 on seawasp, next round  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Mon, Jan 18, 2021 at 09:29:53PM +0100, Fabien COELHO wrote:
>> ... Last two months were a
>> little overworked for me so I let slip quite a few things. If you want to
>> disable the animal as Tom suggests, do as you want.

> Perhaps he was suggesting that you (buildfarm owner) disable the cron job that
> initiates new runs.  That's what I do when one of my animals needs my
> intervention.

Indeed.  I'm not sure there even is a provision to block an animal on the
buildfarm-server side.  If there is, you'd have to request that it be
manually undone after you get around to fixing the animal.  Frankly,
if I were the BF admin, I would be in about as much hurry to do that
as you've been to fix it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Single transaction in the tablesync worker?
Next
From: "kuroda.hayato@fujitsu.com"
Date:
Subject: RE: About to add WAL write/fsync statistics to pg_stat_wal view