Re: [GENERAL] Can't connect to Windows port + other

2004-09-01 Thread Matthew T. O'Connor
Anony Mous wrote: Great, I found the part of the docs referring to this (ch 27.11) however, it refers to creating this file in the user's home directory. It seems this part of the documentation is assuming I'm using *nix. In Windows, where should this file be located? Also, .pgpass is an invalid

Re: [GENERAL] Can't connect to Windows port + other

2004-09-01 Thread Anony Mous
ame in Win. Thanks! -Original Message- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: September 1, 2004 5:19 PM To: Anony Mous Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] Can't connect to Windows port + other "Anony Mous" <[EMAIL PROTECTED]> writes: > If so, w

Re: [GENERAL] Can't connect to Windows port + other

2004-09-01 Thread Robby Russell
On Wed, 2004-09-01 at 16:12, Doug McNaught wrote: > "Anony Mous" <[EMAIL PROTECTED]> writes: > > > A few days ago there was a fellow that had trouble connecting remotely to > > the 8.0 beta win port. I had the same problem, but have since found the > > solution. In postgresql.conf file, ensure t

Re: [GENERAL] Can't connect to Windows port + other

2004-09-01 Thread Tom Lane
"Anony Mous" <[EMAIL PROTECTED]> writes: > If so, why not set the listen_addresses to '*' right away? Security. It was difficult enough to get people to accept the current liberalized default --- I don't think they'll go for defaulting to -i, which is essentially what you're asking for. It's see

Re: [GENERAL] Can't connect to Windows port + other

2004-09-01 Thread Doug McNaught
"Anony Mous" <[EMAIL PROTECTED]> writes: > A few days ago there was a fellow that had trouble connecting remotely to > the 8.0 beta win port. I had the same problem, but have since found the > solution. In postgresql.conf file, ensure the line "listen_addresses" is > set to '*', ie, > > listen_a