Re: Connecting via localhost pg-8.0.3 - Mailing list pgsql-admin

From Tom Lane
Subject Re: Connecting via localhost pg-8.0.3
Date
Msg-id 27553.1118805754@sss.pgh.pa.us
Whole thread Raw
In response to Connecting via localhost pg-8.0.3  (David <dbree@duo-county.com>)
Responses Re: Connecting via localhost pg-8.0.3  (David <dbree@duo-county.com>)
List pgsql-admin
David <dbree@duo-county.com> writes:
> I've just upgraded from 7.4.7 to 8.0.3.

On what platform, and how did you build or obtain each of these PG
versions?

> I get the following error if I omit "host=localhost"  :

> Warning: pg_connect(): Unable to connect to PostgreSQL server: could
> not connect to server: �^@Hv@' Is the server running locally and
> accepting connections on Unix domain socket
> "/var/run/postgresql/.s.PGSQL.5432"? in
> /home/dlb/public_html/test.php
> on line 2

The junk text where a kernel error message ought to be is a known
problem with some older RPM distributions (if running in a non-C
locale) but I thought it was fixed in all known 8.0.3 packagings.
So I'm a tad interested to find where your 8.0.3 came from.

As far as actually solving your problem: it's a good guess that
the problem is a confusion about where the Postgres server socket
lives.  The error message shows that the client library is looking
in /var/run/postgresql/, but the normal default for this is /tmp/.
Do you see a socket file at /tmp/.s.PGSQL.5432 ?  If so then you
have a libpq.so that came from a different build than the server
came from, and the ultimate answer is to get those two components
in sync.

It could well be that both of the above points are explained if
your PHP is linking to an old version of libpq.so that doesn't
match your PG server.

            regards, tom lane

pgsql-admin by date:

Previous
From: "Ricardo Durao"
Date:
Subject: DEADLOCK INSERT
Next
From: Tom Lane
Date:
Subject: Re: Blob error after backup and restore [database > 5.5 Gb.]