On Sat, Jun 27, 2020 at 3:06 PM Peter Eisentraut
<peter.eisentr...@2ndquadrant.com> wrote:
>
> On 2020-06-26 14:21, Amit Kapila wrote:
> > On Sat, Mar 28, 2020 at 7:37 PM Peter Eisentraut <pe...@eisentraut.org>
> > wrote:
> >>
> >> Enable Unix-domain sockets support on Windows
> >>
> >
> > +
> > +/*
> > + * Windows headers don't define this structure, but you can define it
> > yourself
> > + * to use the functionality.
> > + */
> > +struct sockaddr_un
> > +{
> > + unsigned short sun_family;
> > + char sun_path[108];
> > +};
> >
> > I was going through this feature and reading about Windows support for
> > it. I came across a few links which suggest that this structure is
> > defined in <afunix.h>. Is there a reason for not using this via
> > afunix.h?
> >
> > [1] - https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
> > [2] - https://gist.github.com/NZSmartie/079d8f894ee94f3035306cb23d49addc
>
> If we did it that way we'd have to write some kind of configuration-time
> check for the MSVC build, since not all Windows versions have that
> header. Also, not all versions of MinGW have that header (possibly
> none). So the current implementation is probably the most practical
> compromise.
>
Fair enough, but what should be the behavior in the Windows versions
(<10) where Unix-domain sockets are not supported? 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.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
