Received: from laas.laas.fr (root@laas.laas.fr [140.93.0.15]) by hub.org (8.9.3/8.9.3) with ESMTP id EAA80701 for ; Mon, 2 Aug 1999 04:43:56 -0400 (EDT) (envelope-from emarsden@laas.fr) Received: from liszt.laas.fr (liszt [140.93.21.56]) by laas.laas.fr (8.9.3/8.9.3) with ESMTP id KAA22892 for ; Mon, 2 Aug 1999 10:43:54 +0200 (MET DST) Received: (from emarsden@localhost) by liszt.laas.fr (8.9.3/8.9.3) id KAA08980; Mon, 2 Aug 1999 10:44:15 +0200 (MET DST) Sender: emarsden@liszt.laas.fr To: pgsql-interfaces@hub.org Subject: Re: Opening database with PGACCESS References: <199908020431.FAA05810@linda.lfix.co.uk> Organization: LAAS-CNRS http://www.laas.fr/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Eric-Conspiracy: there is no conspiracy X-Attribution: ecm X-URL: http://www.chez.com/emarsden/ From: Eric Marsden Date: 02 Aug 1999 10:44:14 +0200 In-Reply-To: "Oliver Elphick"'s message of Mon, 02 Aug 1999 05:31:08 +0100 Message-ID: Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 >>>>> "oe" == Oliver Elphick writes: rod> "Error connecting database. Connection to database failed rod> connectDB() failed: Is the postmaster running and accepting rod> TCP/IP (with -i) connections at 'localhost' on port '5432'" rod> rod> The postmaster is running and I can connect to mydb using "psql": oe> pgaccess uses a TCP/IP connection through localhost, so you have oe> to use the -i option when starting the postmaster, even though oe> you have no other machines connecting to it. well, there's a trick to get around that. If you provide an empty host name and port number in the pgaccess connection dialog, it will switch to a unix socket connection, and will work even without `-i'. Has worked for me in the past, anyway. -- Eric Marsden It's elephants all the way down