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 1qYvpa-003CTZ-Ke for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 21:56:02 +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 1qYvpZ-0002wY-0P for pgsql-hackers@arkaria.postgresql.org; Wed, 23 Aug 2023 21:56:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYvpY-0002wE-MJ for pgsql-hackers@lists.postgresql.org; Wed, 23 Aug 2023 21:56:00 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYvpV-000eMl-Qf for pgsql-hackers@postgresql.org; Wed, 23 Aug 2023 21:55:59 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 37NLtr4r3565660; Wed, 23 Aug 2023 17:55:53 -0400 From: Tom Lane To: Andres Freund 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? In-reply-to: <20230823214341.stppgfnhrhmb6igf@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> Comments: In-reply-to Andres Freund message dated "Wed, 23 Aug 2023 14:43:41 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3565658.1692827753.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Aug 2023 17:55:53 -0400 Message-ID: <3565659.1692827753@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andres Freund writes: > On 2023-08-23 17:02:51 -0400, Tom Lane wrote: >> ... unless we hit problems with, say, a different default port number o= r >> socket path compiled into one copy vs. the other? That seems like it's >> probably a "so don't do that" case, though. > If we were to find such a case, it seems we could just add whatever miss= ing > parameter to the connection string? I think we would likely already hit = such > problems though, the psql started by an installcheck pg_regress might us= e the > system libpq, I think? The trouble with that approach is that in "make installcheck", we don't really want to assume we know what the installed libpq's default connection parameters are. So we don't explicitly know where that libpq will connect. As I said, we might be able to start treating installed-libpq-not- compatible-with-build as a "don't do it" case. Another idea is to try to ensure that pg_regress uses the same libpq that the psql-under-test does; but I'm not sure how to implement that. regards, tom lane