From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ip connection on local p2p network |
Date: | 2005-04-29 18:43:18 |
Message-ID: | 42728046.4050105@amsoftwaredesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
add the following to pg_hba.conf
host all all 192.0.0.0/8 md5
this will let every PC on you network access the PC
or you could add one entry for each host you would like to have access
host all all 192.0.0.101/32 md5
host all all 192.0.0.102/32 md5
If you don't want to use a password, change md5 to trust.
finally you must modify the postgresql.conf file like so:
(this is what it looks like by default)
#listen_addresses = 'localhost' # what IP interface(s) to listen on;
# defaults to localhost, '*' = any
change it to this:
listen_addresses = '*' # what IP interface(s) to listen on;
# defaults to localhost, '*' = any
notice the listen_addresses is uncommented.
That's all you need to do.
--
Tony Caduto
AM Software Design
Home of PG Lightning Admin for Postgresql 8.x
http://www.amsoftwaredesign.com
typing80wpm(at)aol(dot)com wrote:
> I just installed the windows postgresql on one of the five machines in
> our office, which happens to be 192.0.0.9 according to ipconfig. I
> have installed pg explorer on another machine which happens to be
> 192.0.0.101 .... What changes do I have to make in the various .conf
> files for the postgresql server, (and in pg explorer) so that I can
> connect to the server from the other workstation, hence proving to
> myself that I could use postgres on our small office network. Thanks
> for your help!
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-04-29 19:36:01 | Re: Tuning queries inside a function |
Previous Message | Tim | 2005-04-29 18:43:00 | Re: out of memory for query result |