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 1hxY14-00089s-84 for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Aug 2019 14:43:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hxY12-0003rW-VJ for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Aug 2019 14:43:12 +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 1hxY12-0003rP-ME for pgsql-hackers@lists.postgresql.org; Tue, 13 Aug 2019 14:43:12 +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 1hxY10-0008Bw-4h for pgsql-hackers@postgresql.org; Tue, 13 Aug 2019 14:43:11 +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 x7DEh7ZJ007387; Tue, 13 Aug 2019 10:43:07 -0400 From: Tom Lane To: Feike Steenbergen cc: PostgreSQL mailing lists Subject: Re: Feature: Use DNS SRV records for connecting In-reply-to: References: Comments: In-reply-to Feike Steenbergen message dated "Tue, 13 Aug 2019 11:50:18 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7385.1565707387.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Aug 2019 10:43:07 -0400 Message-ID: <7386.1565707387@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Feike Steenbergen writes: > I'd like to get some feedback on whether or not implementing a DNS SRV f= eature > for connecting to PostgreSQL would be desirable/useful. How would we get at that data without writing our own DNS client? (AFAIK, our existing DNS interactions are all handled by getnameinfo() or other library-supplied functions.) Maybe that'd be worth doing, but it sounds like a lot of work and a lot of new code to maintain, relative to the value of the feature. regards, tom lane