Horton

Re: Unix-domain socket support on Windows

Garick Hamlin <ghamlin@isc.upenn.edu>

View thread View on postgr.es
From: "Hamlin, Garick L" <ghamlin@isc.upenn.edu>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-18T14:24:20Z
Lists: pgsql-hackers 
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?

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.

Garick

Commits

  1. Allow using Unix-domain sockets on Windows in tests

  2. pg_regress: Observe TMPDIR

  3. Enable Unix-domain sockets support on Windows

  4. psql: Remove one use of HAVE_UNIX_SOCKETS

  5. Allow building without default socket directory

  6. Sort out getpeereid() and peer auth handling on Windows