From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bob VonMoss <bvonmoss@bigfoot.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] connecting: unix socket? Yes. TCPIP port? No. -i? Yes.
Date: Sat, 06 Feb 1999 14:01:39 -0500
Message-ID: <20420.918327699@sss.pgh.pa.us> (raw)
In-Reply-To: <36BBBA90.67C72C26@bigfoot.com>
Bob VonMoss <bvonmoss@bigfoot.com> writes:
> [ can connect via unix socket, but not via TCP ]
> The administrator says this is how postmaster is invoked:
> /usr/local/pgsql/bin/postmaster -S -i -D /usr/local/pgsql/data -p 5432
OK, that eliminates the "forgot -i" gotcha.
James Thompson is almost certainly right that the problem is that
Postgres' pg_hba.conf file is not set up to allow connections from
whichever IP address you are connecting from.
We heard about a similar problem recently which turned out to be
due to use of "virtual server" IP addresses. I've forgotten now
whether Postgres saw the connection as coming from the virtual IP
address or the underlying machine's real address, but anyway it wasn't
what the user was expecting :-(.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, bvonmoss@bigfoot.com
Subject: Re: [INTERFACES] connecting: unix socket? Yes. TCPIP port? No. -i? Yes.
In-Reply-To: <20420.918327699@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox