> > > Basically, binding means listening to a specific interface ... since the
> > > remote host IP is not a local IP, you can't listen on that interface ...
> >
> > OK, but how then does -L work? Seems it only accept 127.0.0.1 connections.
>
> it binds the postmaster process to the 127.0.0.1 (localhost) interface
> that is on your computer ... so that if I try to connect 127.0.0.1 on that
> machine, I'll get the postmaster, any other IP on that machine will get me
> a 'connection refused, no such service' ...
>
> Right now, with pg_hba.conf, everything is wide up as far as what
> interface I can connect *to*, and after that connection, then it decides
> if it wants to keep me or not based on my IP ...
>
> actually, my first para isa bit wrong, since nobody but the *loocal*
> machine can connect to 127.0.0.1, since, were you try try, for instance:
>
> telnet 127.0.0.1 smtp
>
> on your machine, you would connect to *your* smtp daemon ...
>
> John's problem is that the software he's wanting to use on the local
> machine requires him to start it up with -i, even though he's *on* the
> local machine, so where he could normally use Unix-Domain Sockets, the app
> can't use it, and he wishes to eliminate the knowledge of PostgreSQL
> running on his machine to the outside world ...
But can't we look at pg_hba.conf and find it only 127.0.0.1 is defined
to accept connections, and if so, use the -L code automatically.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026