Обсуждение: pgaccess startup

Thanks for the advice on regression test - it took 15-20 minutes to
perform the 'numeric' section on my 486.

Next dumb question.

I can (using psql) do more or less what I wish, but this is not an ideal
interface for the public.
While 'pgaccess' (v0.96) starts up okay (now that I have cleared the X
server permission hurdle for user postgres) I have the same problem that
I have had for the past few months.  When I try to open a database, the
following appears:

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 pgaccess page in the postgresql documentation is not
very helpful in this regard, nor can I find relevant information in the
pgaccess documentation (which I would love to rewrite if I get the
chance).

Who would like to point out to me that this simple fact is right under
my nose and would have bitten me long ago if it only had teeth?

Jim

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