| From: | Robby Russell <robby(at)planetargon(dot)com> |
|---|---|
| To: | Doug McNaught <doug(at)mcnaught(dot)org> |
| Cc: | Anony Mous <A(dot)Mous(at)shaw(dot)ca>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Can't connect to Windows port + other |
| Date: | 2004-09-01 23:23:21 |
| Message-ID: | 1094081001.2598.66.camel@vacant |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2004-09-01 at 16:12, Doug McNaught wrote:
> "Anony Mous" <A(dot)Mous(at)shaw(dot)ca> 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_addresses = '*'
> >
> > This should do it. Can someone explain to my why this line is here?
>
> TCP/IP has always been disabled by default, leaving just Unix sockets
> for connections. This is probably not a very useful default
> configuration on Windows. :)
>
> -Doug
Heh, at least it makes the user learn how to configure their postgresql
configuration. ;-)
-Robby
--
/***************************************
* Robby Russell | Owner.Developer.Geek
* PLANET ARGON | www.planetargon.com
* Portland, OR | robby(at)planetargon(dot)com
* 503.351.4730 | blog.planetargon.com
* PHP/PostgreSQL Hosting & Development
****************************************/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anony Mous | 2004-09-01 23:53:58 | Re: Can't connect to Windows port + other |
| Previous Message | Thomas F.O'Connell | 2004-09-01 23:19:45 | Re: Understanding pg_autovacuum CPU Usage |