From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bob VonMoss <bvonmoss(at)bigfoot(dot)com> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] connecting: unix socket? Yes. TCPIP port? No. -i? Yes. |
Date: | 1999-02-06 19:01:39 |
Message-ID: | 20420.918327699@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-interfaces |
Bob VonMoss <bvonmoss(at)bigfoot(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jonny Hinojosa | 1999-02-06 19:13:24 | No MAX function |
Previous Message | Gu feng | 1999-02-06 13:31:41 |
From | Date | Subject | |
---|---|---|---|
Next Message | Pete (Linux) | 1999-02-06 23:45:23 | JDBC-JServ Servlet problem |
Previous Message | KoPra Workshop | 1999-02-06 09:00:26 | postmaster confiugration and hardware configuration |