Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be
	forged)) by hub.org (8.9.3/8.9.3) with ESMTP id TAA02588
	for <pgsql-interfaces@hub.org>; Mon, 5 Jul 1999 19:58:58 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
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 TAA22525;
	Mon, 5 Jul 1999 19:57:53 -0400 (EDT)
To: Jim.Lemon@uts.EDU.AU
cc: pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] pgaccess startup 
In-reply-to: Your message of Mon, 05 Jul 1999 23:09:28 +0000
	<37813B27.D3FF98C4@uts.edu.au>
Date: Mon, 05 Jul 1999 19:57:52 -0400
Message-ID: <22523.931219072@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Jim Lemon <Jim.Lemon@uts.EDU.AU> writes:
> Error connecting database
> Connection to database failed
> connectDB() failed: Is the
> postmaster running and
> accepting TCP/IP (with -i)
> connections at 'localhost' on
> post '5432'?

> This error message changes slightly (and appropriately) when I change
> the host to 'tobermory' (which is the host name).  Unfortunately, I do
> not know what the port number of the postmaster is, nor do I know how to
> find this out.

The default installation uses 5432 as the port number --- if you had
changed that when you installed, you'd probably know it.  My guess is
you didn't start the postmaster with the "-i" command line switch,
so it's not listening for a TCP connection, only Unix socket
connections.

psql will default to trying to connect via a Unix socket, so it'll
still work without -i, but I believe pgaccess always tries TCP/IP
connections, so it won't.  Certainly the above error message indicates
that a TCP/IP connection is being attempted.

There has been some talk of making -i the default postmaster behavior,
but for now it's not.

			regards, tom lane