[GRASSLIST:1154] Re: trouble with g.select.pg

Eric G . Miller egm2 at jps.net
Mon Nov 20 10:54:39 EST 2000

On Mon, Nov 20, 2000 at 11:51:27AM +0100, mlennert at club.worldonline.be wrote:
> I've already sent this message to the sqlgrass-list, but this list doesn't 
> seem very active. Shouldn't we maybe merge it with the main grass list again ?
> ----------------------------------- 
> When trying to run g.select.pg I get the classic error message :
> Error: select Postgres:PQconnectPoll() -- connect() failed: Connection refused
>         Is the postmaster running (with -i) at 'localhost'
>         and accepting connections on TCP/IP port '5432'?
> However, postmaster is running on 5432. I can see the databases with 
> 'g.select.pg -l' and I can connect to them with pg_access. The only thing that 
> seems a bit bizarre is that I cannot enter a host name when connecting through 
> pg_access. If I do I get the same message as above. But when I don't I can 
> connect without any trouble. I remember getting this hint from the pg_access 
> web page or mailing list, so it seems to be a known phenomenon. Could this be 
> the same problem with g.select.pg ?

Yes, I brought this up before.  Seems the code hasn't been changed (I
didn't want to change others code).  The problem is the the interface
with username/password pairs.  The code should be sending user=NULL,
password=NULL, hostname=NULL, but instead sends hostname="localhost",
which causes a TCP/IP connection vs. a UNIX socket, which will probably
make your configuration demand a valid username/password pair.  It's
definitely a bug, IMHO.

Eric G. Miller <egm2 at jps.net>

More information about the grass-user mailing list