You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Since HAVE_UNIX_SOCKETS is now defined unconditionally, remove the macroand drop a small amount of dead code.The last known systems not to have them (as far as I know at least) wereQNX, which we de-supported years ago, and Windows, which now has them.If a new OS ever shows up with the POSIX sockets API but without workingAF_UNIX, it'll presumably still be able to compile the code, and fail atruntime with an unsupported address family error. We might want toconsider adding a HINT that you should turn off the option to use it ifyour network stack doesn't support it at that point, but it doesn't seemworth making the relevant code conditional at compile time.Also adjust a couple of places in the docs and comments that referred tobuilds without Unix-domain sockets, since there aren't any. Windowsstill gets a special mention in those places, though, because we don'ttry to use them by default there yet.Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>Reviewed-by: Andres Freund <andres@anarazel.de>Reviewed-by: Peter Eisentraut <peter.eisentraut@enterprisedb.com>Discussion:https://postgr.es/m/CA%2BhUKG%2BL_3brvh%3D8e0BW_VfX9h7MtwgN%3DnFHP5o7X2oZucY9dg%40mail.gmail.com