pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: test/modules/test_oat_hooks vs. debug_discard_caches=1
Date: Sat, 19 Nov 2022 10:30:40 -0500
Message-ID: <e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net> (raw)
In-Reply-To: <2393660.1668868402@sss.pgh.pa.us>
References: <2267406.1668804934@sss.pgh.pa.us>
	<20221119003349.uzpopxq2skgrmwc4@awork3.anarazel.de>
	<2316565.1668827411@sss.pgh.pa.us>
	<9ce14134-5725-5b9f-e27e-f4002ff13a4e@enterprisedb.com>
	<c0701701-b2c2-3499-c60d-4b7fbbafb0f3@dunslane.net>
	<1bbb0340-3dbe-717a-4094-a4344238245b@enterprisedb.com>
	<2393660.1668868402@sss.pgh.pa.us>


On 2022-11-19 Sa 09:33, Tom Lane wrote:
> Tomas Vondra <tomas.vondra@enterprisedb.com> writes:
>> On 11/19/22 14:51, Andrew Dunstan wrote:
>>> On 2022-11-19 Sa 05:34, Tomas Vondra wrote:
>>>> I wonder if it'd make sense to have some simple & optional alerting
>>>> based on how long ago the machine reported the last result. Send e-mail
>>>> if there was no report for a month or so would be enough.
>>> This has been part of the buildfarm for a very long time. See the alerts
>>> section of the config file.
>> I don't think alerting from the client would catch those cases, but
>> maybe it's a rare issue and I'm overthinking it.
> Those alerts are sent by the buildfarm server, not the client.
>
> That has a failure mode of its own: if an animal goes down hard,
> the server is left with its last-seen alert setup.  The only
> way to not get nagged permanently is to ask Andrew to intervene
> manually.  (Ask me how I know.)
>
> 			


True for now. The next release will have a utility command to
disable/enable alerts. The required server changes have already been made.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com






view thread (9+ messages)

Message-ID: <e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net>
Permalink:  ../e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net/
Also on:    postgresql.org/message-id/e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers@postgresql.org
  Cc: andrew@dunslane.net, tgl@sss.pgh.pa.us, tomas.vondra@enterprisedb.com, andres@anarazel.de
  Subject: Re: test/modules/test_oat_hooks vs. debug_discard_caches=1
  In-Reply-To: <e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net>
  References: <2267406.1668804934@sss.pgh.pa.us> <20221119003349.uzpopxq2skgrmwc4@awork3.anarazel.de> <2316565.1668827411@sss.pgh.pa.us> <9ce14134-5725-5b9f-e27e-f4002ff13a4e@enterprisedb.com> <c0701701-b2c2-3499-c60d-4b7fbbafb0f3@dunslane.net> <1bbb0340-3dbe-717a-4094-a4344238245b@enterprisedb.com> <2393660.1668868402@sss.pgh.pa.us> <e20bb3bb-3d2f-5221-59d4-b3ecb5a82a5d@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox