Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nXryv-0004w7-4U for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Mar 2022 22:00:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nXryt-0006bY-8M for pgsql-hackers@arkaria.postgresql.org; Fri, 25 Mar 2022 22:00:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nXrys-0006bP-VJ for pgsql-hackers@lists.postgresql.org; Fri, 25 Mar 2022 22:00:26 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nXryq-0005Jf-Sz for pgsql-hackers@postgresql.org; Fri, 25 Mar 2022 22:00:25 +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 22PM0Msj3482590; Fri, 25 Mar 2022 18:00:22 -0400 From: Tom Lane To: Jacob Champion cc: "robertmhaas@gmail.com" , "andrew@dunslane.net" , "pgsql-hackers@postgresql.org" Subject: Re: [PATCH] Enable SSL library detection via PQsslAttribute In-reply-to: References: <4c8b76ef434a96627170a31c3acd33cbfd6e41f1.camel@vmware.com> <6c4b2233-a8ad-4952-960c-6293243f1f96@dunslane.net> <83541b1e7873f2adb862f7f3ec763fae30a731b5.camel@vmware.com> Comments: In-reply-to Jacob Champion message dated "Fri, 25 Mar 2022 21:25:37 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3482588.1648245622.1@sss.pgh.pa.us> Date: Fri, 25 Mar 2022 18:00:22 -0400 Message-ID: <3482589.1648245622@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion writes: > Do I need to merge my tiny test program into the libpq_pipeline tests? Doesn't seem worth the trouble to me, notably because you'd then have to cope with non-SSL builds too. regards, tom lane