Thread

1. running pgaccess on localhost

   Mike Goetz <nospam@home.com> — 2001-04-27T08:24:53Z

   Hello, pgsql newbie here...
   
   I'm trying to run pgaccess on a database I've created, and I get the
   following error:
   
   PostgreSQL error message: Connection to database failed 
   PQconnectPoll() -- connect() failed: Connection refused
   Is the postmaster running (with -i) at 'localhost' and accepting
   connections on TCP/IP port '5432'?
   
   Now the postmaster is not normally set up with the -i option, and I'd like
   to keep it that way since I'm intending to use my workstation for local
   development only (are there any security issues by activating the -i
   option?).  Indeed turning the -i option on does in fact allow me to use
   pgaccess without error.
   
   However, since I'm running pgaccess from a terminal window on my machine I
   would have thought that this would constitute a local domain socket
   connection (or at least a connection from the localhost), so I'm confused
   by the error message -- am I missing something or do I really have to
   enable TCP/IP connections if I want to initiate database access using
   pgacess from a terminal window?
   
   Mike
   
   [running postgreSQL 7.0 on Linux-Mandrake with kernel 2.4.3]
   
   

2. Re: running pgaccess on localhost

   Joel Burton <jburton@scw.org> — 2001-04-27T14:51:39Z

   On Fri, 27 Apr 2001, Mike Goetz wrote:
   
   > Hello, pgsql newbie here...
   > 
   > I'm trying to run pgaccess on a database I've created, and I get the
   > following error:
   > 
   > PostgreSQL error message: Connection to database failed 
   > PQconnectPoll() -- connect() failed: Connection refused
   > Is the postmaster running (with -i) at 'localhost' and accepting
   > connections on TCP/IP port '5432'?
   > 
   > Now the postmaster is not normally set up with the -i option, and I'd like
   > to keep it that way since I'm intending to use my workstation for local
   > development only (are there any security issues by activating the -i
   > option?).  Indeed turning the -i option on does in fact allow me to use
   > pgaccess without error.
   > 
   > However, since I'm running pgaccess from a terminal window on my machine I
   > would have thought that this would constitute a local domain socket
   > connection (or at least a connection from the localhost), so I'm confused
   > by the error message -- am I missing something or do I really have to
   > enable TCP/IP connections if I want to initiate database access using
   > pgacess from a terminal window?
   
   The fact that you're running pgaccess from a term window doesn't mean that
   pgaccess connects to PG w/a local socket.
   
   Someone may know how to configure pgaccess to use a local socket. If not,
   use the -i switch, and edit $PGDATA/pg_hba.conf to block access from other
   machines. (This is the default setting.)
   
   
   
   -- 
   Joel Burton   <jburton@scw.org>
   Director of Information Systems, Support Center of Washington
   
   
   

3. Re: running pgaccess on localhost

   Eric G. Miller <egm2@jps.net> — 2001-04-30T14:46:13Z

   On Fri, Apr 27, 2001 at 08:24:53AM +0000, Mike Goetz wrote:
   > Hello, pgsql newbie here...
   > 
   > I'm trying to run pgaccess on a database I've created, and I get the
   > following error:
   > 
   > PostgreSQL error message: Connection to database failed 
   > PQconnectPoll() -- connect() failed: Connection refused
   > Is the postmaster running (with -i) at 'localhost' and accepting
   > connections on TCP/IP port '5432'?
   > 
   > Now the postmaster is not normally set up with the -i option, and I'd like
   > to keep it that way since I'm intending to use my workstation for local
   > development only (are there any security issues by activating the -i
   > option?).  Indeed turning the -i option on does in fact allow me to use
   > pgaccess without error.
   > 
   > However, since I'm running pgaccess from a terminal window on my machine I
   > would have thought that this would constitute a local domain socket
   > connection (or at least a connection from the localhost), so I'm confused
   > by the error message -- am I missing something or do I really have to
   > enable TCP/IP connections if I want to initiate database access using
   > pgacess from a terminal window?
   
   Try not specifying a hostname or port in the login window.  Then it
   should use the local unix socket method (I think).
   
   -- 
   Eric G. Miller <egm2@jps.net>