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 1qYv9w-0039oA-UC for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 21:13:00 +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 1qYv9v-00HF4i-LL for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 21:12:59 +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 1qYv9v-00HF2z-98 for pgsql-hackers@lists.postgresql.org; Wed, 23 Aug 2023 21:12:59 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYv9r-000akn-97 for pgsql-hackers@postgresql.org; Wed, 23 Aug 2023 21:12:57 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 16C402FA70FE for ; Wed, 23 Aug 2023 23:12:52 +0200 (CEST) Received: from s980.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 06EE52E2B435; Wed, 23 Aug 2023 23:12:52 +0200 (CEST) Received: from s475.loopia.se (unknown [172.22.191.6]) by s980.loopia.se (Postfix) with ESMTP id 040E62201658; Wed, 23 Aug 2023 23:12:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Received: from s981.loopia.se ([172.22.191.5]) by s475.loopia.se (s475.loopia.se [172.22.190.15]) (amavisd-new, port 10024) with LMTP id ktAXico0OFRe; Wed, 23 Aug 2023 23:12:51 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s981.loopia.se (Postfix) with ESMTPSA id 63D0322B17C6; Wed, 23 Aug 2023 23:12:51 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Cirrus-ci is lowering free CI cycles - what to do with cfbot, etc? From: Daniel Gustafsson In-Reply-To: <3557216.1692824571@sss.pgh.pa.us> Date: Wed, 23 Aug 2023 23:12:50 +0200 Cc: Andres Freund , PostgreSQL Hackers , Thomas Munro , Justin Pryzby , Nazir Bilal Yavuz Content-Transfer-Encoding: quoted-printable Message-Id: References: <20230808021541.7lbzdefvma7qmn3w@awork3.anarazel.de> <20230823065833.vnnfwoi3n2sbw5kf@awork3.anarazel.de> <20230823192239.jxew5s3sjru63lio@awork3.anarazel.de> <3557216.1692824571@sss.pgh.pa.us> To: Tom Lane X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 23 Aug 2023, at 23:02, Tom Lane wrote: >=20 > Daniel Gustafsson writes: >> On 23 Aug 2023, at 21:22, Andres Freund wrote: >>> I think there's more effective ways to make this cheaper. The basic = thing >>> would be to use libpq instead of forking of psql to make a = connection >>> check. >=20 >> I had it in my head that not using libpq in pg_regress was a = deliberate choice, >> but I fail to find a reference to it in the archives. >=20 > I have a vague feeling that you are right about that. Perhaps the > concern was that under "make installcheck", pg_regress might be > using a build-tree copy of libpq rather than the one from the > system under test. As long as we're just trying to ping the server, > that shouldn't matter too much I think ... unless we hit problems > with, say, a different default port number or socket path compiled = into > one copy vs. the other? That seems like it's probably a "so don't > do that" case, though. Ah yes, that does ring a familiar bell. I agree that using it for = pinging the server should be safe either way, but we should document the = use-with-caution in pg_regress.c if/when we go down that path. I'll take a stab at = changing the psql retry loop for pinging tomorrow to see what it would look like. -- Daniel Gustafsson