Обсуждение: PostgreSQL 9.1 not connecting

Michael Rowan <michael.rowan3@gmail.com> wrote:

>
> I checked pg_hba.conf and postgresql.conf (listen_address = '*', port=5432)

Do you have propper hosts - entries in your pg_hba.conf for the other
host?


Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°

Hi

Utter novice would be glad of another hand here.

I have two Mac OSX 10.6.8 servers each with an iMac workstation OSX 10.6.8, so two seemingly identical setups.

Each server has an identical (as far as I can see) PG 9.1 installation and pgAdmin3 works fine on both with (copies of)  the same data.

Using an Omnis Studio client app, one workstation will connect (always has), the other will not (used to but not now). It gives no clue as to the problem.

I checked pg_hba.conf and postgresql.conf (listen_address = '*', port=5432)

Is there a way to get some debug feedback?  Glad to have any help.

Michael

-- 
siamo arrivati sani e salvi

Michael Rowan <michael.rowan3@gmail.com> writes:
> Utter novice would be glad of another hand here.

> I have two Mac OSX 10.6.8 servers each with an iMac workstation OSX 10.6.8,
> so two seemingly identical setups.

> Each server has an identical (as far as I can see) PG 9.1 installation and
> pgAdmin3 works fine on both with (copies of)  the same data.

> Using an Omnis Studio client app, one workstation will connect (always
> has), the other will not (used to but not now). It gives no clue as to the
> problem.

Third-party apps with no useful error handling are such fun, aren't they.

> I checked pg_hba.conf and postgresql.conf (listen_address = '*', port=5432)

The other obvious configuration point to check is whether the OS' firewall
is configured to allow incoming connections to Postgres.

If that's not it, I'd try to connect using psql or some other app that
actually tells you something about connection failures.  The postmaster's
log file in the Postgres installation might be helpful as well, especially
if you turn on log_connections.

            regards, tom lane