Horton

Re: Unix-domain socket support on Windows

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-16T08:58:19Z
Lists: pgsql-hackers 
On 2019-12-16 05:39, Andrew Dunstan wrote:
> On Wed, Oct 30, 2019 at 10:32 PM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
>>
>> To move this topic a long, I'll submit some preparatory patches in a
>> committable order.
>>
>> First is the patch to deal with getpeereid() that was already included
>> in the previous patch series.  This is just some refactoring that
>> reduces the difference between Windows and other platforms and prepares
>> the Unix-domain socket specific code to compile cleanly on Windows.
>>
> 
> 
> This looks fairly sane and straightforward. Let's give it an outing on
> the buildfarm ASAP so we can keep moving forward on this.

pushed

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

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