> <<TCP/IP is enabled by default on Windows. Your problem is somewhere > else>> > This is not bourne out by my experience or the document you > referenced. > The document and postgresql.conf both state that the default > is 'localhost' and only allows local loopback connections.
Default is 'localhost'. This is TCP/IP. Which is different from Unix sockets. Since Unix sockets aren't available on Windows, you need TCP/IP to be able to connect at all. That said, I think I may have misread the original question as actually wanting "remote TCP/IP" connections. The comment about the clients IP certainly implies so. In which case my answer was clearly wrong! Sorry to mislead you :-) //Magnus > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Magnus Hagander > Sent: Wednesday, September 29, 2004 10:52 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: [ADMIN] TCP/IP access in Postgresql 8 Windows > > > > Hi, > > > > I'm pretty versed in Postgresql version 7.* on Linux. Need > to setup a > > 8.* server on Windows. Postgresql 8 is rejecting TCP/IP > connections. > > Tried to acivate tcpip_sockets, as in the 7.4.* versions, > configuring > > postgresql.conf param tcpip_sockets, but it is not recognized by > > version 8 (it even fails to start if included). Client IP's have an > > entry in pg_hba.conf. > > > > Is there any other task that must be done in order to get TCP/IP > > connections working? > > TCP/IP is enabled by default on Windows. Your problem is > somewhere else > - check for local firewall or antivirus sofware that might be > blocking the connection. > > tcpip_sockets has been renamed to listen_addresses. Check > http://developer.postgresql.org/docs/postgres/runtime-config.h > tml#RUNTIM > E-CONFIG-CONNECTION. > > > //Magnus > > ---------------------------(end of > broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > > ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
