| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG vs LLVM 12 on seawasp, next round |
| Date: | 2021-01-25 04:06:18 |
| Message-ID: | 1698296.1611547578@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kuroda.hayato@fujitsu.com | 2021-01-25 04:09:44 | RE: About to add WAL write/fsync statistics to pg_stat_wal view |
| Previous Message | Amit Kapila | 2021-01-25 03:54:25 | Re: Single transaction in the tablesync worker? |