"Don Oliver" <dayo_nanaimo(at)hotmail(dot)com> writes:
> PostgreSQL is always on, and works fine from the command line. (A console in
If you mean that "psql" works, that's good, but by default psql tries to
connect via a Unix socket file, not via TCP/IP. So TCP connection
problems won't necessarily show up. If you use the -h option then psql
tries to use a TCP connection, which is what pgaccess always tries.
I'll bet if you do "psql -h localhost" you see the same failure as in
> If I try to start pgaccess with: "pgaccess don", the main PgAccess window
> comes up,
> (empty) but there is an error message box in front of it. The message is:
> "Error trying to connect to database "don" on host localhost.
> PostgreSQL error message: Connection to database failed:
> Network is unreachable. is the postmaster running (with -i) at
> 'localhost' and accepting connections on TCP/IP port '5432'?"
The critical part of that message is the "Network is unreachable" part,
which is the kernel error message that pgaccess is getting when it tries
to connect. That's a pretty darn bizarre error code to get for an
attempt to contact 'localhost'. I think there's something screwy in
the networking configuration of your machine. Dunno what exactly;
but it likely doesn't have anything directly to do with Postgres.
If you do, say, "telnet localhost 23", do you get a telnet login prompt
or an error?
regards, tom lane
In response to
pgsql-interfaces by date
|Next:||From: Jesse Scott||Date: 2000-03-02 07:51:14|
|Subject: Postgres on MacOS... Is it even a possibility?|
|Previous:||From: Byron Nikolaidis||Date: 2000-03-02 03:44:21|
|Subject: Re: [INTERFACES] Access, Views and the OID|