Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iF0Hk-0002T9-D6 for pgsql-committers@arkaria.postgresql.org; Mon, 30 Sep 2019 18:20:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iF0Hi-0005yM-QX for pgsql-committers@arkaria.postgresql.org; Mon, 30 Sep 2019 18:20:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iF0Hi-0005y9-JL for pgsql-committers@lists.postgresql.org; Mon, 30 Sep 2019 18:20:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iF0Hg-0002bP-HY for pgsql-committers@lists.postgresql.org; Mon, 30 Sep 2019 18:20:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x8UIKT0I019003; Mon, 30 Sep 2019 14:20:29 -0400 From: Tom Lane To: Jeff Davis cc: Michael Paquier , Jeff Davis , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Add libpq parameter 'channel_binding'. In-reply-to: <11a5c3b483f1c0140f9fc5cf863d8ac61a28e60a.camel@j-davis.com> References: <24857.1569775891@sss.pgh.pa.us> <20190929234733.GA2888@paquier.xyz> <20190930064539.GK2888@paquier.xyz> <20190930070826.GM2888@paquier.xyz> <11a5c3b483f1c0140f9fc5cf863d8ac61a28e60a.camel@j-davis.com> Comments: In-reply-to Jeff Davis message dated "Mon, 30 Sep 2019 11:14:47 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19001.1569867629.1@sss.pgh.pa.us> Date: Mon, 30 Sep 2019 14:20:29 -0400 Message-ID: <19002.1569867629@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jeff Davis writes: > For 2-3, shouldn't we error at an earlier stage? The user of the client > has requested something impossible to satisfy. Can't get excited about that. It'd require duplicating this code somewhere else, which is a maintenance issue. And the case of building with obsolete OpenSSL ought to be fairly infrequent and getting more so as time goes on, so I'm not really eager to expend lots of work on it. regards, tom lane