pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-admin@postgresql.org
Cc: Hilton Perantunes <hperantunes@gmail.com>
Subject: Re: Yet Another Socket .s.PGSQL.5432 Problem
Date: Fri, 17 Aug 2007 11:09:24 +0200
Message-ID: <200708171109.25370.peter_e@gmx.net> (raw)
In-Reply-To: <b24a8cca0708161441y1fee6786r55ba2290faa2c35@mail.gmail.com>
References: <b24a8cca0708151313k43c05849y8906967046775a2b@mail.gmail.com>
	<20070816212517.GC27775@alvh.no-ip.org>
	<b24a8cca0708161441y1fee6786r55ba2290faa2c35@mail.gmail.com>

Am Donnerstag, 16. August 2007 23:41 schrieb Hilton Perantunes:
> Alvaro, it works like a charm =). Thank you all.
>
> Bad, bad Debian.. no cookies for you (and I'll read the error messages more
> carefully next time)!

The problem is quite likely some variant on the following:  You had your 
distribution-supplied PostgreSQL packages installed, which 
use /var/run/postgresql as the socket location.  Then you built your own 
pieces of PostgreSQL, which use /tmp.  When you call just "psql" 
or "pgadmin3", they will use the system-supplied libpq, which uses the 
system-specific socket location, since they don't know about your 
hand-crafted installation.  If you had called the psql binary from your own 
installation with an explicit path (and your used the rpath feature during 
compilation), then this would have worked.  Or you could have used the 
environment variable LD_LIBRARY_PATH to point to the libpq of your choice.  
There are a few ways to get this wrong.  On Debian the socket location is 
usually the first indicator, but you ought to be careful in general if you 
mix installations like that.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/



view thread (10+ messages)  latest in thread

Message-ID: <200708171109.25370.peter_e@gmx.net>
Permalink:  ../200708171109.25370.peter_e@gmx.net/
Also on:    postgresql.org/message-id/200708171109.25370.peter_e@gmx.net

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: peter_e@gmx.net, hperantunes@gmail.com
  Subject: Re: Yet Another Socket .s.PGSQL.5432 Problem
  In-Reply-To: <200708171109.25370.peter_e@gmx.net>

* 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