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 1ihbnm-00038I-6F for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Dec 2019 16:03:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihbnl-0001q9-03 for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Dec 2019 16:03:53 +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 1ihbnj-0001q2-OC for pgsql-hackers@lists.postgresql.org; Wed, 18 Dec 2019 16:03:52 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ihbnf-0001aA-Jy for pgsql-hackers@postgresql.org; Wed, 18 Dec 2019 16:03:51 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B4B8A66F; Wed, 18 Dec 2019 11:03:44 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 18 Dec 2019 11:03:44 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fmCshxl/h7P0H2ijpoB0X3m9X53yzefk90qRHsH1O Gs=; b=msJRz+oAhqMUch9paOh9CPO4PmkwJS9vHHacQy1qT/6J91/UyNMlgTVNk 64cA5wPggQaMJdgltwSviVbuEyjZSy0DoYlCUYZWS3RNkkOXnNrx3KblHp/KnXBJ HGoUKj8Xl2FbYvYKFHA7k+zSKrwkSbMDQG4xyI+jMW43H/AvXUfyWQzNDbSHm2wR d3r1uTfQ07yqgtlvgYF9Eebqr3nxG5DX1AHRBrygiJpx7b5rdhuRX3BYKH07wuYV 8bC16f7yUh2y5pALli+D286Q4BHZ/vn/UBRssWXe7pwZp/MkcFCcKmiu2b1QnazZ ifrOgSe1XHr8zKskFA9ITtuvnCBew== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvddtledgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegvddrudeiuddrudeftdenucfrrghrrghmpehmrghilhhfrh homhepphgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm necuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from april.pezone.net (p5df2a182.dip0.t-ipconnect.de [93.242.161.130]) by mail.messagingengine.com (Postfix) with ESMTPA id 0927280059; Wed, 18 Dec 2019 11:03:42 -0500 (EST) Subject: Re: Unix-domain socket support on Windows To: "Hamlin, Garick L" References: <54bde68c-d134-4eb8-5bd3-8af33b72a010@2ndquadrant.com> <00d4945e-b437-f3b5-f4af-42e99321c846@2ndquadrant.com> <5974caea-1267-7708-40f2-6009a9d653b0@2ndquadrant.com> <75f72249-8ae6-322a-63df-4fe03eeccb9f@2ndquadrant.com> <20191218142419.fvv4ikm4wq4gnkco@isc.upenn.edu> Cc: Andrew Dunstan , pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <5231fafe-bda0-5a4d-d75b-c83d96ee5758@2ndquadrant.com> Date: Wed, 18 Dec 2019 17:03:40 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20191218142419.fvv4ikm4wq4gnkco@isc.upenn.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-12-18 15:24, Hamlin, Garick L wrote: > On Wed, Dec 18, 2019 at 02:52:15PM +0100, Peter Eisentraut wrote: >> To implement this, tweak things so that setting DEFAULT_PGSOCKET_DIR >> to "" has the desired effect. This mostly already worked like that; >> only a few places needed to be adjusted. Notably, the reference to >> DEFAULT_PGSOCKET_DIR in UNIXSOCK_PATH() could be removed because all >> callers already resolve an empty socket directory setting with a >> default if appropriate. > > Would it make sense to support abstract sockets in PostgreSQL? Maybe, I'm not sure. > I know it's bit unrelated. I haven't read all the code here I just was > thinking about it because of the code checking the leading \0 byte of the dir. We would probably represent abstract sockets with a leading '@' in the user-facing components and only translate it to the internal format at the last moment, probably in that very same UNIXSOCK_PATH() function. So I think that wouldn't be a problem. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services