Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYwmM-003Gbh-9d for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 22:56:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qYwmK-000p3k-Gw for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 22:56:44 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYwmI-000p3O-IY for pgsql-hackers@lists.postgresql.org; Wed, 23 Aug 2023 22:56:43 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYwmA-000bcq-7d for pgsql-hackers@postgresql.org; Wed, 23 Aug 2023 22:56:40 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id C1E815C01D8; Wed, 23 Aug 2023 18:56:32 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 23 Aug 2023 18:56:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1692831392; x=1692917792; bh=oH sVr8abpIY+sjOvsswllK5TAYNMfRWPCDJUqibZW9E=; b=EKtktMeT2bBxCV8DVJ LCs5NEykX7HZKDtJDWN9T+KVwZwKSCE6i4Xsa1su+FMwrxXUyh+ZckCk2jltGs4T 3KNikh4oox6W5vJnBbqtMaTKZX2/ZwVTrCdPUEiKRvMAf35Z4syJwJOYuRroww7y ena73O6ag6asZx4reIvQTSHl7wqujKTbmr/5rPhQgruJncqwWQAPN8e04qRolel9 I7vBasbRF3TbQTkLkejcBqswz3Npli1d2EZR3h7eZW6rTFMB9E2bgh4KnAUmEUxx 2oPbfSSMXhvvI2thJUvooP/G3y2XWmgegwomu2MNl8tkqpCGGek3MsMzb3UP4W52 +XzA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1692831392; x=1692917792; bh=oHsVr8abpIY+s jOvsswllK5TAYNMfRWPCDJUqibZW9E=; b=U25O/bUdqgYdn5vm5iD+9iU55jrrx 9hfsayn6NMcA8Vc+I/I2fi3OISyEX3030vcqIszWrCFe++yKHxFf9OBfFip3sPSB 18iXWnr4dD7yImmiw67MVPYkc64pq5G5PeILr3qTPH5sVD6sq2SrbtgKLHxM7fOb VIg4auxvLooE4UW3hBSZ2CaAFhOFpVJ5k8JLKWP+FAgYBKf/gqSVAs0OjrZM2cYP VQNnhdEEspBs4+14pZM1z3nOSV4RbHaj0qvYsNqNq9wOSz4jaJktiiselBXKDWI3 YfUcyTN/ACHRyB6uphWux+cJDzz3WJtIefacArzU2VnzjqLF5TVi+Fl8g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedruddvhedgudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughr vghsucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrf grthhtvghrnhepvdfffeevhfetveffgeeiteefhfdtvdffjeevhfeuteegleduheetvedu ieettddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh eprghnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 23 Aug 2023 18:56:31 -0400 (EDT) Date: Wed, 23 Aug 2023 15:56:30 -0700 From: Andres Freund To: Tom Lane Cc: Daniel Gustafsson , PostgreSQL Hackers , Thomas Munro , Justin Pryzby , Nazir Bilal Yavuz Subject: Re: Cirrus-ci is lowering free CI cycles - what to do with cfbot, etc? Message-ID: <20230823225630.npitkolsqh4q2bv2@awork3.anarazel.de> References: <20230808021541.7lbzdefvma7qmn3w@awork3.anarazel.de> <20230823065833.vnnfwoi3n2sbw5kf@awork3.anarazel.de> <20230823192239.jxew5s3sjru63lio@awork3.anarazel.de> <3557216.1692824571@sss.pgh.pa.us> <20230823214341.stppgfnhrhmb6igf@awork3.anarazel.de> <3565659.1692827753@sss.pgh.pa.us> <20230823220612.sglm5g5oxblunst3@awork3.anarazel.de> <3570610.1692829946@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3570610.1692829946@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2023-08-23 18:32:26 -0400, Tom Lane wrote: > Andres Freund writes: > > There are other potential uses for libpq in pg_regress though - I'd e.g. like > > to have a "monitoring" session open, which we could use to detect that the > > server crashed (by waiting for the FD to be become invalid). Where the > > connection default issue could matter more? > > Meh. I don't find that idea compelling enough to justify adding > restrictions on what test scenarios will work. It's seldom hard to > tell from the test output whether the server crashed. I find it pretty painful to wade through a several-megabyte regression.diffs to find the cause of a crash. I think we ought to use restart_after_crash=false, since after a crash there's no hope for the tests to succeed, but even in that case, we end up with a lot of pointless contents in regression.diffs. If we instead realized that we shouldn't start further tests, we'd limit that by a fair bit. Greetings, Andres Freund