Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.8.8/8.7.5) with ESMTP id JAA22744 for ; Fri, 21 Aug 1998 09:59:40 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA15239; Fri, 21 Aug 1998 09:59:34 -0400 (EDT) To: "Roeland M.J. Meyer" cc: pgsql-interfaces@hub.org Subject: Re: [INTERFACES] Remote access ODBC/MS-Access In-reply-to: Your message of Thu, 20 Aug 1998 23:58:39 -0700 <199808210658.XAA19347@condor.mhsc.com> Date: Fri, 21 Aug 1998 09:59:33 -0400 Message-ID: <15237.903707973@sss.pgh.pa.us> From: Tom Lane "Roeland M.J. Meyer" writes: >> postgres@condor:/rdbms$> psql customerdb >> Connection to database 'customerdb' failed. >> connectDB() failed: Is the postmaster running at 'raven.mhsc.com' on port > '5432'? If you look at the code in src/interfaces/libpq/fe-connect.c, you'll find this message is generated if the connect() system call fails, which means you don't have connectivity to the postmaster. You need not worry about whether the database exists or whether hba.conf allows you to connect, because none of those conditions can be checked until the postmaster receives the startup request packet from the client --- and your client is not even getting as far as sending that packet. A quick-and-dirty point is did you start the postmaster with -i on its command line? If not it won't be listening for TCP connections, only unix-socket connections. Otherwise it seems like you must have an addressing or physical connectivity problem of some kind... regards, tom lane