pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David <dbree@duo-county.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David <dbree@duo-county.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Connecting via localhost pg-8.0.3
Date: Wed, 15 Jun 2005 21:00:48 -0500
Message-ID: <20050616020048.GA1912@localhost.localdomain> (raw)
In-Reply-To: <27553.1118805754@sss.pgh.pa.us>
References: <20050615022603.GA1615@localhost.localdomain>
	<27553.1118805754@sss.pgh.pa.us>

On Tue, Jun 14, 2005 at 11:22:34PM -0400, Tom Lane wrote:
> 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?

Oops - thought I included that but apparently didn't..

Platform is Debian. The packages come from The Debian repositories.

> > 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.

Well, you guessed correctly.  It was a configuration problem.  By
inserting the line:
        unix_socket_directory = '/var/run/postgresql'
into postgresql.conf, it works as expected.

I must confess that I was a bit unclear about the connection parameters.
I thought that (in php) "host=localhost" meant to use sockets, but this
means connect through TCP/IP over lo, correct?

> 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.

I'd wondered if this could have been it, but apparently all appears to
be satisfactory now.

Thanks for the reply.  It got me headed in the right direction.



view thread (5+ messages)  latest in thread

Message-ID: <20050616020048.GA1912@localhost.localdomain>
Permalink:  ../20050616020048.GA1912@localhost.localdomain/
Also on:    postgresql.org/message-id/20050616020048.GA1912@localhost.localdomain

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: dbree@duo-county.com, tgl@sss.pgh.pa.us
  Subject: Re: Connecting via localhost pg-8.0.3
  In-Reply-To: <20050616020048.GA1912@localhost.localdomain>
  References: <20050615022603.GA1615@localhost.localdomain> <27553.1118805754@sss.pgh.pa.us> <20050616020048.GA1912@localhost.localdomain>

* 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