Skip setsockopt(SO_REUSEADDR) for the Unix-domain postmaster socket on

all platforms, not just SCO.  The operation is undefined for Unix-domain
sockets anyway.  It seems SCO is not the only platform that complains
instead of treating the call as a no-op.
This commit is contained in:
Tom Lane 2000-04-14 00:51:58 +00:00
parent bf00aec8d0
commit 07672d4e0a
2 changed files with 1 additions and 9 deletions

View File

@ -29,7 +29,7 @@
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc
* Portions Copyright (c) 1994, Regents of the University of California
*
* $Id: pqcomm.c,v 1.88 2000/04/12 17:15:14 momjian Exp $
* $Id: pqcomm.c,v 1.89 2000/04/14 00:51:58 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -205,11 +205,8 @@ StreamServerPort(char *hostName, unsigned short portName, int *fdP)
return STATUS_ERROR;
}
#ifdef ONLY_REUSE_INET_SOCKETS
if (family == AF_INET)
{
#endif
if ((setsockopt(fd, SOL_SOCKET, SO_REUSEADDR, (char *) &one,
sizeof(one))) == -1)
{
@ -220,10 +217,7 @@ StreamServerPort(char *hostName, unsigned short portName, int *fdP)
pqdebug("%s", PQerrormsg);
return STATUS_ERROR;
}
#ifdef ONLY_REUSE_INET_SOCKETS
}
#endif
MemSet((char *) &saddr, 0, sizeof(saddr));
saddr.sa.sa_family = family;

View File

@ -2,8 +2,6 @@
#define NOFILE NOFILES_MIN
#endif
#define ONLY_REUSE_INET_SOCKETS
#define DISABLE_COMPLEX_MACRO
#define USE_POSIX_TIME