From e645cc2ab80450b18227931082beefc2bb8ffb0a Mon Sep 17 00:00:00 2001 From: Thomas Munro Date: Mon, 15 Aug 2022 10:43:13 +1200 Subject: [PATCH 4/4] Doc: Abstract AF_UNIX sockets don't work on Windows after all. An early release of AF_UNIX in Windows might have supported Linux-style "abstract" Unix sockets with a system-wide namespace, but they do not seem to work in current Windows versions and there is no mention of any of this in the Winsock documentation. Remove the claim that it works from our documentation. Back-patch to 14, where commit c9f0624b landed. Discussion: https://postgr.es/m/20220813223646.oh2dkjrkj7jn7dpe%40awork3.anarazel.de --- doc/src/sgml/config.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 39d1c89e33..55286375dc 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -759,7 +759,7 @@ include_dir 'conf.d' A value that starts with @ specifies that a Unix-domain socket in the abstract namespace should be created - (currently supported on Linux and Windows). In that case, this value + (currently supported on Linux). In that case, this value does not specify a directory but a prefix from which the actual socket name is computed in the same manner as for the file-system namespace. While the abstract socket name prefix can be -- 2.38.1