Re: pgsql: Enable Unix-domain sockets support on Windows - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pgsql: Enable Unix-domain sockets support on Windows
Date
Msg-id bb7422d1-15cf-b26b-4e63-2660c8e324eb@2ndquadrant.com
Whole thread Raw
In response to Re: pgsql: Enable Unix-domain sockets support on Windows  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: pgsql: Enable Unix-domain sockets support on Windows  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On 2020-06-27 13:57, Amit Kapila wrote:
> Fair enough, but what should be the behavior in the Windows versions
> (<10) where Unix-domain sockets are not supported?

You get an error about an unsupported address family, similar to trying 
to use IPv6 on a system that doesn't support it.

> BTW, in which
> format the path needs to be specified for unix_socket_directories?  I
> tried with '/c/tmp', 'c:/tmp', 'tmp' but nothing seems to be working,
> it gives me errors like: "could not create lock file
> "/c/tmp/.s.PGSQL.5432.lock": No such file or directory" on server
> start.  I am trying this on Win7 just to check what is the behavior of
> this feature on it.

Hmm, the only thing I remember about this now is that you need to use 
native Windows paths, meaning you can't just use /tmp under MSYS, but it 
needs to be something like C:\something.  But the error you have there 
is not even about the socket file but about the lock file, which is a 
normal file, so if that goes wrong, it might be an unrelated problem.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Fwd: PostgreSQL: WolfSSL support
Next
From: Daniel Gustafsson
Date:
Subject: Re: PostgreSQL: WolfSSL support